ACK/NACK transmission for multi-carrier operation with downlink assignment index

ABSTRACT

Techniques for acknowledging data transmissions in a multi-carrier wireless communication network are disclosed. In one aspect, a UE determines a number of acknowledgement/negative acknowledgement (ACK/NACK) bits for a data transmission on one more component carriers (CCs) based on information obtained from a grant. The grant may be a downlink grant or an uplink grant, and the information obtained may include a number of CCs scheduled for data transmission and/or identifiers of the scheduled CCs. The UE may determine the number of ACK/NACK bits for acknowledging the data transmission based on the number of scheduled CCs and the identifier of each scheduled CC.

The present application claims priority to provisional U.S. ApplicationSer. No. 61/374,210, entitled “METHODS AND APPARATUS FOR ACK/NACKRELATED DESIGN FOR CARRIER AGGREGATION IN LTE-A NETWORKS,” filed Aug.16, 2010, and incorporated herein by reference in its entirety.

BACKGROUND

I. Field

The present disclosure relates generally to communication and, morespecifically, to techniques for supporting communication in amulti-carrier wireless communication network.

II. Background

Wireless communication networks are widely deployed to provide variouscommunication content such as voice, video, packet data, messaging,broadcast, etc. These wireless networks may be multiple-access networkscapable of supporting multiple users by sharing the available networkresources. Examples of such multiple-access networks include CodeDivision Multiple Access (CDMA) networks, Time Division Multiple Access(TDMA) networks, Frequency Division Multiple Access (FDMA) networks,Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA)networks.

A wireless communication network may include a number of base stationsthat can support communication for a number of user equipments (UEs). AUE may communicate with a base station via the downlink and uplink. Thedownlink (or forward link) refers to the communication link from thebase station to the UE, and the uplink (or reverse link) refers to thecommunication link from the UE to the base station.

A wireless communication network may support operation on multiplecomponent carriers (CCs). A CC may refer to a range of frequencies usedfor communication and may be associated with certain characteristics.For example, a CC may be associated with system information describingoperation on the CC. A CC may also be referred to as a carrier, a cell,a serving cell, a frequency channel, etc.

SUMMARY

Techniques for acknowledging data transmissions in a multi-carrierwireless communication network are disclosed. In one aspect, a UEdetermines a number of acknowledgement/negative acknowledgement(ACK/NACK) bits to send for a data transmission on one more componentcarriers (CCs) based on information obtained from a grant. The grant maybe a downlink grant or an uplink grant, and the information obtained mayinclude a number of CCs scheduled for data transmission and/oridentifiers of the scheduled CCs. The UE may determine the number ofACK/NACK bits for acknowledging the data transmission based on thenumber of scheduled CCs and the identifier of each scheduled CC.

In one aspect, the UE may determine a transmission mode of eachscheduled CC. The UE may determine the total number of ACK/NACK bitsbased on the transmission mode of each scheduled CC and the number ofscheduled CCs. In another aspect, the UE may determine a number oftransport blocks received on each scheduled CC and a total number oftransport blocks received in the data transmission. The UE may use thetotal number of ACK/NACK bits and/or the total number of receivedtransport blocks for various purposes including (i) determination of atransmit power for sending the ACK/NACK information on a PUCCH, (ii)determination of a number of resource elements for sending the ACK/NACKinformation on a PUSCH, (iii) determination of a number of bitsavailable to multiplex channel state information (CSI) with the ACK/NACKinformation, and/or (iv) other purposes.

Various additional aspects and features of the disclosure are describedin further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a wireless communication network.

FIG. 2 shows an exemplary frame structure for frequency divisionduplexing.

FIG. 3 shows an exemplary frame structure for time division duplexing.

FIGS. 4A and 4B show examples of carrier aggregation.

FIG. 5 shows aspects of data transmission on multiple CCs with HARQ.

FIG. 6 shows an example of determining an ACK/NACK bitwidth in amulti-carrier wireless communication network.

FIG. 7 shows an example of a downlink assignment index (DAI) for amulti-carrier wireless communication network.

FIG. 8 shows a process for sending ACK/NACK information.

FIG. 9 shows a process for receiving ACK/NACK information.

FIG. 10 shows an exemplary base station and an exemplary UE, which canperform the exemplary processes described herein.

FIG. 11 shows further aspects of base station and a UE according to thepresent disclosure.

DETAILED DESCRIPTION

The techniques described herein may be used for various wirelesscommunication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother wireless networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA), Time Division Synchronous CDMA (TD-SCDMA), andother variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856standards. A TDMA network may implement a radio technology such asGlobal System for Mobile Communications (GSM). An OFDMA network mayimplement a radio technology such as Evolved UTRA (E-UTRA), Ultra MobileBroadband (UMB), IEEE 802.11 (Wi-Fi and Wi-Fi Direct), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are part ofUniversal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) and LTE-Advanced (LTE-A), in both frequency divisionduplexing (FDD) and time division duplexing (TDD), are new releases ofUMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA onthe uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, certain aspects of the techniquesare described below for LTE, and LTE terminology is used in much of thedescription below.

FIG. 1 shows a wireless communication network 100, which may be an LTEnetwork or some other wireless network. Wireless network 100 may includea number of evolved Node Bs (eNBs) 110 and other network entities. AneNB may be an entity that communicates with the UEs and may also bereferred to as a Node B, a base station, an access point, etc. Each eNBmay provide communication coverage for a particular geographic area andmay support communication for the UEs located within the coverage area.To improve network capacity, the overall coverage area of an eNB may bepartitioned into multiple (e.g., three) smaller areas. Each smaller areamay be served by a respective eNB subsystem. In 3GPP, the term “cell”can refer to a coverage area of an eNB and/or an eNB subsystem servingthis coverage area. In general, an eNB may support one or multiple(e.g., three) cells. The term “cell” may also refer to a carrier onwhich an eNB operates.

A network controller 130 may couple to a set of eNBs and providecoordination and control for these eNBs. Network controller 130 maycommunicate with the eNBs via a backhaul. The eNBs may also communicatewith one another, e.g., directly or indirectly via wireless or wirelinebackhaul.

UEs 120 may be dispersed throughout the wireless network, and each UEmay be stationary or mobile. A UE may also be referred to as a mobilestation, a terminal, an access terminal, a subscriber unit, a station,etc. A UE may be a cellular phone, a smart phone, a tablet, a wirelesscommunication device, a personal digital assistant (PDA), a wirelessmodem, a handheld device, a laptop computer, a cordless phone, awireless local loop (WLL) station, a netbook, a smartbook, etc. Forclarity, some of the description below refers to UE 120 x and eNB 110 x,which may be one of the UEs and one of the eNBs in wireless network 100.

LTE utilizes orthogonal frequency division multiplexing (OFDM) on thedownlink and single-carrier frequency division multiplexing (SC-FDM) onthe uplink. OFDM and SC-FDM partition a frequency spectrum into multiple(N_(FFT)) orthogonal subcarriers, which are also commonly referred to astones, bins, etc. Each subcarrier may be modulated with data. Ingeneral, modulation symbols are sent in the frequency domain with OFDMand in the time domain with SC-FDM. The spacing between adjacentsubcarriers may be fixed, and the total number of subcarriers (N_(FFT))may be dependent on the system bandwidth. For example, the subcarrierspacing may be 15 kilohertz (KHz), and N_(FFT) may be equal to 128, 256,512, 1024 or 2048 for system bandwidth of 1.4, 3, 5, 10 or 20 megahertz(MHz), respectively.

Wireless network 100 may utilize FDD or TDD. For FDD, the downlink anduplink may be allocated separate frequency spectrum. Downlinktransmissions may be sent on one frequency spectrum, and uplinktransmissions may be sent on another frequency spectrum. For TDD, thedownlink and uplink may share the same frequency spectrum, and downlinkand uplink transmissions may be sent on the same frequency spectrum indifferent time intervals.

FIG. 2 shows an exemplary frame structure 200 for FDD in LTE. Thetransmission timeline for each of the downlink and uplink may bepartitioned into units of radio frames. Each radio frame may have apredetermined duration (e.g., 10 milliseconds (ms)) and may bepartitioned into 10 subframes with indices of 0 through 9. Each subframemay include two slots. Each slot may include L symbol periods, e.g.,seven symbol periods for a normal cyclic prefix (as shown in FIG. 2) orsix symbol periods for an extended cyclic prefix. The 2 L symbol periodsin each subframe may be assigned indices of 0 through 2 L−1.

The available time frequency resources for each of the downlink anduplink may be partitioned into resource blocks. Each resource block maycover 12 subcarriers in one slot and may include a number of resourceelements. Each resource element may cover one subcarrier in one symbolperiod and may be used to send one modulation symbol, which may be areal or complex value.

FIG. 3 shows an exemplary frame structure 300 for TDD in LTE. Subframes0 and 5 are used for the downlink, subframe 2 is used for the uplink,and subframes 3, 4, 7, 8 and 9 may each be used for the downlink oruplink. Subframe 1 includes a Downlink Pilot Time Slot (DwPTS), a GuardPeriod (GP), and an Uplink Pilot Time Slot (UpPTS). Subframe 6 mayinclude only the DwPTS, or all three special fields, or a downlinksubframe. LTE supports a number of uplink-downlink configurations forTDD. Each uplink-downlink configuration indicates whether each subframeis a downlink subframe, an uplink subframe, or a special subframe. Theremay be as many as nine downlink subframes to one uplink subframe in aradio frame.

As shown in FIGS. 2 and 3, a subframe for the downlink (i.e., a downlinksubframe) may include a control region and a data region, which may betime division multiplexed (TDM). The control region may include thefirst Q symbol periods of the subframe, where Q may be equal to 1, 2, 3or 4. Q may change from subframe to subframe and may be conveyed in thefirst symbol period of the subframe. The data region may include theremaining 2 L−Q symbol periods of the subframe and may carry data and/orother information for UEs.

An eNB may send downlink control information (DCI) on a physicaldownlink control channel (PDCCH) in the control region to a UE. The DCImay include a downlink grant, an uplink grant, power controlinformation, etc. The eNB may send data and/or other information on aphysical downlink shared channel (PDSCH) in the data region to the UE.

As shown in FIGS. 2 and 3, a subframe for the uplink (i.e., an uplinksubframe) may include a control region and a data region, which may befrequency division multiplexed (FDM). The control region may includeresource blocks near the two edges of the uplink spectrum (as shown inFIGS. 2 and 3) and may have a configurable size. The data region mayinclude all resource blocks not included in the control region.

A UE may send uplink control information (UCI) to an eNB on a physicaluplink control channel (PUCCH) in the control region of an uplinksubframe. The UCI may include ACK/NACK information for a datatransmission received on the downlink, channel state information (CSI),scheduling request (SR), etc. The UE may send data or data and UCI tothe eNB on a physical uplink shared channel (PUSCH) in the data regionof the uplink subframe. The UE may transmit only the PUCCH or only thePUSCH (and not both) in a subframe in order to maintain a single-carrierwaveform, which may have a lower peak-to-average power ratio (PAPR). Anuplink transmission may span both slots of a subframe and may hop acrossfrequency.

Wireless network 100 may support multi-carrier operation on multiple CCson the downlink and one or more CCs on the uplink. Operation on multipleCCs may be referred to as carrier aggregation. A CC for the downlink maybe referred to as a downlink CC, and a CC for the uplink may be referredto as an uplink CC. An eNB may transmit data and DCI on one or moredownlink CCs to a UE. A data transmission may include a transmission ofone or more transport blocks (which may also be referred to as a PDSCHtransmission) on each of at least one CC. For example, in a givensubframe, the UE may receive multiple PDSCH transmissions on multipleconfigured CCs. The UE may transmit data and UCI to the eNB on one ormore uplink CCs.

FIG. 4A shows an example of continuous carrier aggregation. In thisexample, M CCs are shown as adjacent to each other in frequency, where Mmay be any integer value. Each CC may have a bandwidth of 20 MHz or lessand may be separately configured for a UE.

FIG. 4B shows an example of non-continuous carrier aggregation. In thisexample, M CCs are shown as separated from each other in frequency. Eachnon-contiguous CC may have a bandwidth of 20 MHz or less and may beseparately configured for a UE.

With carrier aggregation, data and control information may beindependently sent and received on each CC. This may be achieved, forexample, by using (i) a separate inverse fast Fourier transform (IFFT)and a separate transmitter for each CC at a transmitting entity and (ii)a separate fast Fourier transform (FFT) and a separate receiver for eachCC at a receiving entity. A transmission comprising up to M concurrentOFDM symbols or SC-FDMA symbols may be on up to M CCs in one symbolperiod. In another example, data and control information may becollectively sent and received on all CCs. This may be achieved by using(i) a single IFFT and a single transmitter for all M CCs at atransmitting entity and (ii) a single FFT and a single receiver for allM CCs at a receiving entity. A single OFDM symbol or SC-FDMA symbol maybe transmitted on up to M CCs in one symbol period.

Wireless network 100 may support data transmission with hybrid automaticretransmission (HARQ) in order to improve reliability. For HARQ, atransmitter (e.g., an eNB) may send an initial transmission of atransport block and may send one or more additional transmissions of thetransport block, if needed, until the transport block is decodedcorrectly by a receiver (e.g., a UE), or the maximum number oftransmissions of the transport block has occurred, or some othertermination condition is encountered. After each transmission of thetransport block, the receiver may send an acknowledgement (ACK) if thetransport block is decoded correctly, a negative acknowledgement (NACK)if the transport block is decoded in error, or a discontinuoustransmission (DTX) if the transport block is missed. The transmitter maysend another transmission of the transport block if a NACK or a DTX isreceived and may terminate transmission of the transport block if an ACKis received. A transport block may also be referred to as a packet, acodeword, a data block, etc.

FIG. 5 shows a scheme of transmitting DCI and data with HARQ on multiple(M) downlink CCs and transmitting UCI and data on one uplink CC. In thisexample, UE 120 x may periodically estimate the channel quality ofdifferent downlink CCs for eNB 110 x and may determine CSI for eachdownlink CC. The CSI may include channel quality indicator (CQI),precoding matrix indicator (PMI), rank indicator (RI), or a combinationthereof. RI may indicate the number of layers or spatial channels to usefor transmission of data. PMI may indicate a precoding matrix or vectorto use for precoding data prior to transmission. CQI may indicate achannel quality for each transport block. UE 120 x may send CSI for eachdownlink CC to eNB 110 x periodically or when triggered.

eNB 110 x may use the CSI and/or other information to select UE 120 xfor transmission of data, to schedule UE 120 x on one or more downlinkCCs and/or the uplink CC, and to select one or more modulation andcoding schemes (MCSs) for each downlink CC on which UE 120 x isscheduled. eNB 110 x may process (e.g., encode and modulate) one or moretransport blocks for each scheduled CC based on the one or more MCSsselected for that CC. eNB 110 x may then send a transmission of one ormore transport blocks (or a PDSCH transmission) on each scheduled CC toUE 120 x.

UE 120 x may receive and decode the transmission of one or moretransport blocks on each scheduled CC in the plurality of configuredCCs. For each configured CC, UE 120 x may determine whether atransmission of one or more transport blocks is detected and, when atransmission is detected, whether each transport block is decodedcorrectly or in error. UE 120 x may generate an ACK for each transportblock decoded correctly and a NACK for each transport block decoded inerror. UE 120 x may send ACK/NACK information comprising ACKs and/orNACKs for all transport blocks received on all M downlink CCs in aparticular subframe.

eNB 110 x may receive the ACK/NACK information from UE 120 x, terminatetransmission of each transport block for which an ACK is received, andsend another transmission of each transport block for which a NACK isreceived. UE 120 x may also transmit data to eNB 110 x with the ACK/NACKinformation when there is data to send and when it has been scheduledfor transmission of data on the uplink CC.

As shown in FIG. 5, eNB 110 x may send a downlink (DL) grant for a PDSCHtransmission on a downlink CC to UE 120 x. The downlink grant mayinclude various parameters for receiving and decoding the PDSCHtransmission on the downlink CC. The downlink grant may be sent on thedownlink CC on which the PDSCH transmission is sent or on anotherdownlink CC. eNB 110 x may also send an uplink (UL) grant for a datatransmission on the uplink CC by UE 120 x. The uplink grant may includevarious parameters for generating and sending the data transmission on ashared channel (e.g., PUSCH) of the uplink CC. The uplink grant may alsoinclude a CQI request. In this case, UE 120 x may send CSI with data onthe PUSCH.

UE 120 x may transmit data and/or UCI, or neither, in a given subframe.The UCI may comprise only CSI, or only ACK/NACK, or both CSI andACK/NACK. UE 120 x may be configured to periodically send CSI for eachdownlink CC of interest, which may be referred to as periodic CQIreporting. In this case, the UE may periodically send CSI reports indesignated subframes determined by a schedule for periodic CSIreporting. Each CSI report may comprise CQI, PMI and/or RI for one ormore downlink CCs. UE 120 x may also be requested to send CSI for one ormore downlink CCs in any subframe, which may be referred to as aperiodicCSI reporting. This may be achieved by including a CSI request for oneor more downlink CCs in an uplink grant.

eNB 110 x may send DCI (e.g., a downlink grant and/or an uplink grant)to UE 120 x on the PDCCH on a downlink CC. When UE 120 x is scheduledfor a data transmission, eNB 110 x may send data on the PDSCH on adownlink CC. In a particular subframe, UE 120 x may send UCI (e.g., CSIand/or ACK/NACK) on the PUCCH on an uplink CC to eNB 110 x.Alternatively, when an uplink grant is received, UE 120 x may send onlydata or both data and UCI on the PUSCH on an uplink CC.

In general, UE 120 x may be configured with any number of downlink CCsand any number of uplink CCs for multi-carrier operation. For instance,UE 120 x may be configured with up to five downlink CCs and up to fiveuplink CCs for multi-carrier operation. In some examples, one downlinkCC may be designated as a downlink primary CC (PCC), one uplink CC maybe designated as an uplink PCC, and each remaining CC may be referred toas a secondary CC (SCC). eNB 110 x may send certain information (e.g.,grants, ACK/NACK, etc.) on the downlink PCC to UE 120 x. UE 120 x maysend certain information (e.g., CSI, ACK/NACK, scheduling request, etc.)on the uplink PCC to eNB 110 x.

Table 1 lists different types of CC referred to in the descriptionherein.

TABLE 1 CC Type CC Type Description Configured CC A downlink CC that isconfigured for UE 120x. Activated CC A downlink CC that is configuredand activated/enabled for use. Scheduled CC A downlink CC on which UE120x is scheduled for data transmission. Detected CC A downlink CC onwhich UE 120x receives a data transmission.

UE 120 x may be semi-statically configured with M downlink CCs and oneor more uplink CCs, e.g., via higher layer such as Radio ResourceControl (RRC). In general, M may be any value greater than one. In oneexemplary system, M may be less than or equal to five. Some or all ofthe configured CCs may be activated. An activated CC is a CC that a UEactively monitors on the downlink and/or actively transmits on theuplink. UE 120 x may not monitor a deactivated CC on the downlink, eventhough the CC is one of the configured CCs, which would result in powersavings. UE 120 x may be scheduled for data transmission on all or asubset of the configured CCs in a given subframe. For dynamicscheduling, a downlink grant may be sent for a transmission of one ormore transport blocks on each scheduled CC.

UE 120 x may detect a downlink grant on the PDCCH for a PDSCHtransmission on a downlink CC (a “detected CC”). UE 120 x may receivethe PDSCH transmission on the detected CC in accordance with thedownlink grant. The downlink grant may be sent on the same downlink CCon which the associated PDSCH transmission is sent. In this case, thedetected CC would be the downlink CC on which the downlink grant isreceived. The downlink grant may also be sent on one downlink CC, andthe associated PDSCH transmission may be sent on a different downlinkCC. For example, the downlink grant may include a carrier indicationfield (CIF) indicating the downlink CC on which the associated PDSCHtransmission is sent. In that case, UE 120 x may identify the detectedCC based on the CIF in the downlink grant. UE 120 x may detect some orall of the scheduled CCs, e.g., depending on whether UE 120 x missed anydownlink grants sent to UE 120 x. UE 120 x may receive PDSCHtransmissions on all detected CCs.

UE 120 x may be configured with M downlink CCs, and each downlink CC maybe associated with a particular transmission mode in a set of supportedtransmission modes. Table 2 lists the transmission modes supported inLTE Release 9. Transmission modes 1, 2, 5, 6 and 7 support single-inputsingle-output (SISO) or single-input multiple-output (SIMO)transmissions. Transmission modes 3, 4 and 8 support multiple-inputmultiple-output (MIMO) transmission.

TABLE 2 Transmission Modes Number of Transmission Transport Mode BlocksDescription 1 1 Transmission from a single eNB antenna port 2 1 Transmitdiversity 3 2 Open-loop spatial multiplexing 4 2 Closed-loop spatialmultiplexing 5 1 Multi-user MIMO 6 1 Closed-loop rank 1 precoding 7 1Transmission using UE-specific reference signal 8 2 Dual layertransmission

A transmission mode may be independently configured for each downlinkCC. The M downlink CCs for UE 120 x may be configured with the same ordifferent transmission modes.

One or more transport blocks may be sent on a downlink CC depending onthe transmission mode configured for the downlink CC. In particular, onetransport block may be sent on a downlink CC that is configured withtransmission mode 1, 2, 5, 6 or 7, and two transport blocks may be senton a downlink CC that is configured with transmission mode 3, 4 or 8. UE120 x may generate one ACK/NACK bit for each transport block. Forexample, one ACK/NACK bit may used to acknowledge a data transmission ona CC configured in transmission mode 1, 2, 5, 6 or 7 and two ACK/NACKbits may be used to acknowledge a data transmission on a CC configuredin transmission mode 3, 4 or 8.

The number of ACK/NACK bits for acknowledging a transmission of one ormore transport blocks on a downlink CC may also be dependent on a DCIformat of a corresponding downlink grant. LTE supports a number of DCIformats. DCI format 1, 1A, 1B, 1C or 1D may be used to send a downlinkgrant for a transmission of one transport block and may thus beassociated with one ACK/NACK bit. DCI formats 2, 2A or 2B may be used tosend a downlink grant for a transmission of two transport blocks and maythus be associated with two ACK/NACK bits. A DCI format of a downlinkgrant may be associated with a particular number of transport blocks tosend on a downlink CC, which may be different from (e.g., fewer than)the number of transport blocks associated with a transmission modeconfigured for the downlink CC. For example, CCj may be configured witha transmission mode supporting two transport blocks but may be scheduledwith a downlink grant having a DCI format used with one transport block.In that case, eNB 110 x may send one transport block on CCx and UE 120 xmay generate one bit of ACK/NACK information to acknowledge the datatransmission on CCj.

In one example, UE 120 x may be configured with five downlink CCs formulti-carrier operation in FDD. In this case, in a given subframe, eNB110 x may send up to ten transport blocks on up to five downlink CCs,with up to two transport blocks per downlink CC. Up to ten ACK/NACK bitsmay be obtained for up to ten transport blocks, one ACK/NACK bit foreach transport block (up to 12 ACK/NACK bits may be obtained if DTX isexplicitly signaled). UE 120 x may thus have N ACK/NACK bits for a datatransmission over M configured downlink CCs, where 1≦M≦N≦10.

According to the present disclosure, techniques for determining thenumber of ACK/NACK bits for a data transmission on M downlink CCs in amulti-carrier wireless communication network are described. The numberof ACK/NACK bits for acknowledging a data transmission may be determinedin different manners depending on the availability of certaininformation. The number of ACK/NACK bits, in turn, may be used tocontrol transmission of ACK/NACK information. In one aspect, a downlinkassignment index (DAI) may be used to facilitate determination of thenumber of ACK/NACK bits for a data transmission on M downlink CCs. A DAImay be included in a downlink grant and may indicate the number ofdownlink CCs scheduled and/or may provide an indication of whichdownlink CCs are scheduled. The DAI may help UE 120 x to detect missingdownlink grants, facilitate more efficient ACK/NACK feedback, and/orprovide other advantages.

The total number of ACK/NACK bits for M configured CCs may be referredto as the ACK/NACK bitwidth, the ACK/NACK payload size, etc. TheACK/NACK bitwidth may be dependent on whether ACK/NACK bits fordifferent downlink CCs are ordered or non-ordered. The use of ordered ornon-ordered feedback may be configured for UE 120 x. For the non-orderedcase, ACK/NACK bits for the M configured CCs may be concatenated in apredetermined order, e.g., based on an index of each downlink CC. Forthe ordered case, ACK/NACK bits for the M configured CCs may beconcatenated by first considering ACK/NACK bits for the scheduled CCsand then considering ACK/NACK bits for the remaining CCs.

FIG. 6 shows an example of determining ACK/NACK bitwidth for the orderedand non-ordered cases. In this example, UE 120 x is configured with fivedownlink CCs (CC1-CC5). CC2 and CC5 are associated with 1-bit ACK/NACKfeedback (e.g., based on transmission mode and DCI format as previouslydiscussed). CC1, CC3 and CC4 are associated with 2-bit ACK/NACKfeedback. Only CC2, CC3 and CC4 are scheduled in a particular subframe.A set of bits to be encoded and sent as ACK/NACK feedback may bedetermined as follows:

-   -   Non-ordered case: ‘00’ (CC1)+1 bit (CC2)+2 bits (CC3)+2 bits        (CC4)+‘0’(CC5)+zeros, or    -   Ordered case: 1 bit (CC2)+2 bits (CC3)+2 bits (CC4)+zeros.

ACK/NACK information may be sent on the PUCCH or PUSCH in a fixedpayload size. In this case, zero padding with a sufficient number ofzeros may be performed to obtain a set of bits of the proper payloadsize.

The non-ordered case may result in simpler operation since one or twoACK/NACK bits for each configured CC may be readily obtained from theACK/NACK feedback based on the CC index and the number of ACK/NACK bitsfor each configured CC. However, the ordered case may have betterefficiency since the ACK/NACK bits for the scheduled CCs are placedfirst and may thus result in fewer bits being used for ACK/NACKfeedback. In some examples, CSI and/or other information may bemultiplexed in the remaining bits of the payload after ACK/NACKinformation for the scheduled carriers is added.

Table 3 lists three DAI schemes for multi-carrier operation according tothe present disclosure. In the first scheme, a DAI is not included indownlink grants. In the second and third schemes, a DAI is supported andconveys different information. Determination of ACK/NACK bitwidth basedon each of the three schemes is described below.

TABLE 3 DAI Schemes Scheme Description First No DAI Downlink grant doesnot include DAI. Scheme Second DAI indicates Downlink grant includes DAIindicating Scheme number of number of downlink CCs scheduled inscheduled CCs a subframe. Third DAI identifies Downlink grant includesDAI indicating Scheme scheduled CCs number of downlink CCs and whichdownlink CCs are scheduled in a subframe.

In the second scheme, the DAI indicates the number downlink CCs beingscheduled and may be set to a value within a range of 1 to M−1. In oneexample, the DAI may have a variable width, which may be dependent on M.For example, the DAI may include one bit for M=2, two bits for M=3 or 4,or three bits for M=5. In another example, the DAI may have a fixedwidth (e.g., of three bits) that is independent of M. The DAI may beincluded in a downlink grant for each scheduled CC or for only certainscheduled CCs.

In the third scheme, the DAI indicates the number of downlink CCs beingscheduled as well as which downlink CCs are scheduled. The DAI may beincluded in a downlink grant for a scheduled CC and may indicate whichother downlink CCs (if any) are also scheduled. The DAI may be definedin different manners for the third scheme.

In a first variation of the third scheme, the DAI may have a variablewidth that is dependent on M. The number of bits used for the DAI may besmaller than the number of configured CCs. For example, if M=1, then theDAI may be omitted. If M=2, then the DAI may comprise one bit and may beset to (i) a first value (e.g., ‘0’) to indicate one downlink CC beingscheduled, which is the downlink CC associated with the downlink grantincluding the DAI, or (ii) a second value (e.g., ‘1’) to indicate twodownlink CCs being scheduled. If M=3, then the DAI may comprise two bitsand may be set to (i) a first value (e.g., ‘00’) to indicate onedownlink CC being scheduled, (ii) a second value (e.g., ‘01’) toindicate a first remaining downlink CC also being scheduled, (iii) athird value (e.g., ‘10’) to indicate a second remaining downlink CC alsobeing scheduled, or (iv) a fourth value (e.g., ‘11’) to indicate allthree downlink CCs being scheduled.

To further illustrate this design, consider the case of three configuredCCs (CCx, CCy and CCz). The eNB may set the DAI in a downlink grant forCCx to the second value to indicate that CCy is scheduled, or to thethird value to indicate that CCz is scheduled. If M=4, a 3-bit DAI maybe utilized. The DAI may be set to (i) a first value to indicate onedownlink CC being scheduled, (ii) a second, a third, or a fourth valueto indicate one other downlink CC also being scheduled among the threeremaining downlink CCs, (iii) a fifth, a sixth, or a seventh value toindicate two other downlink CCs also being scheduled among the threeremaining downlink CCs, or (iv) an eight value to indicate all fourdownlink CCs being scheduled.

Continuing with the example, a 4-bit DAI may be utilized when M=5. TheDAI may be set to (i) a first value to indicate one downlink CC beingscheduled, (ii) a value within the 2nd through 5th value to indicate oneother downlink CC also being scheduled among the four remaining downlinkCCs, (iii) a value within the 6th through 11th value to indicate twoother downlink CCs also being scheduled among the four remainingdownlink CCs, (iv) a value within the 12th through 14th value toindicate three other downlink CCs also being scheduled among the fourremaining downlink CCs, or (v) a 15th value to indicate all fivedownlink CCs being scheduled. When the variable width DAI of the thirdscheme is utilized, UE 120 x may be able to determine how many downlinkCCs and which downlink CCs are scheduled based on the DAI in onedownlink grant for one scheduled CC.

In another variation of the third scheme, the DAI may comprise a bitmapof M−1 bits, with one bit for each remaining downlink CC (not includingthe downlink CC on which the PDCCH is received). The bit for eachremaining downlink CC may be set to a first value (e.g., ‘0’) toindicate the downlink CC is not scheduled or to a second value (e.g.,‘1’) to indicate the downlink CC is scheduled. The number of downlinkCCs being scheduled may be equal to 1 (for the downlink CC associatedwith a downlink grant carrying the DAI) plus the number of ones in thebitmap.

FIG. 7 shows an example of the DAI for the bitmap variation of the thirdscheme. In this example, the DAI is included in a downlink grant for aPDSCH transmission on downlink CC2 and comprises a bitmap of M−1 bitsfor M−1 other downlink CCs. The bit for CC1 is set to ‘0’ to indicateCC1 not being scheduled, the bit for CC3 is set to ‘1’ to indicate CC3being scheduled, etc. UE 120 x may receive the DAI in a downlink grantfor a PDSCH transmission on one scheduled CC. Based on the DAI, UE 120 xcan determine all scheduled CCs based on the DAI in the receiveddownlink grant, even if it does not detect the downlink grants for allof the other scheduled CCs.

In another variation of the third scheme, the DAI may comprise a limitednumber of bits, and only some scheduled CCs may be identified by theDAI. For example, the DAI may comprise two bits (instead of M−1 bits)even when more than two downlink CCs are scheduled. In this variation,the downlink PCC may be given higher priority than the downlink SCCs.For M=3, the DAI can identify each downlink CC that is scheduled, asdescribed above. For M=4, the DAI in a downlink grant for the PCC mayinclude one bit covering two SCCs and another bit covering the last SCC.The DAI in a downlink grant for an SCC may include one bit covering thePCC and another bit covering the other two SCCs. For M=5, the DAI in adownlink grant for the PCC may include one bit covering two SCCs andanother bit covering the last two SCCs. The DAI in a downlink grant foran SCC may include one bit covering the PCC and another bit covering theother three SCCs. With this variation, two or more entries may share thesame DAI value. For example, the same DAI value (e.g., ‘00’) may be usedfor the case of one scheduled CC and another case of four scheduled CCs,since the probability of confusion between these two cases may be small.This may allow for a tradeoff between overhead and ambiguity in theinformation provided by the DAI.

As described herein, further variations of the DAI may also utilizedwith the second and third schemes. In addition, the DAI may conveydifferent information depending upon the CC configuration for aparticular UE such that different DAI schemes may be utilized withdifferent CC configurations or in support of different UEs.

A DAI indicating the number of scheduled CCs and/or identifying thescheduled CCs may be sent in various manners. In one example, the DAImay be included in each downlink grant sent on the PDCCH for eachscheduled CC. In another example, the DAI may be included only indownlink grants for the downlink PCC. In yet another example, the DAImay be included in one or more downlink grants for one or moredesignated CCs, e.g., the first and last CCs. Additionally oralternatively, a DAI for downlink data transmission may be included inan uplink grant sent on the PDCCH. This design may provide additionalprotection against missed detection of the PDCCH by a UE.

The ACK/NACK bitwidth for M configured CCs may be determined in variousmanners for the three schemes listed in Table 3. Some exemplary designsof determining the ACK/NACK bitwidth are described below.

For the first scheme with no DAI, an exemplary ACK/NACK bitwidth for Mconfigured CCs may be determined as follows:

$\begin{matrix}{{n_{HARQ} = {\sum\limits_{C \in {{Configured}\_{Set}}}n_{C}}},} & {{Eq}\mspace{14mu}(1)}\end{matrix}$where n_(C) is the number of ACK/NACK bits for downlink CC C,

-   -   n_(HARQ) is the total number of ACK/NACK bits for M configured        CCs, and Configured_Set denotes a set of configured CCs.

n_(HARQ) is the ACK/NACK bitwidth for the M configured CCs. n_(HARQ) inequation (1) may be the same for both the ordered and non-ordered cases.

In another design, the ACK/NACK bitwidth for cases where no DAI isprovided may be determined as follows:

$\begin{matrix}{{n_{HARQ} = {\sum\limits_{C \in {{Activated}\_{Set}}}n_{C}}},} & {{Eq}\mspace{14mu}(2)}\end{matrix}$where Activated_Set denotes a set of activated CCs. The set of activatedCCs may include all or a subset of the M configured CCs.

In yet another design, in the absence of DAI, the ACK/NACK bitwidth maybe determined as follows:

$\begin{matrix}{{n_{HARQ} = {\sum\limits_{C \in {{Detected}\_{Set}}}n_{C}}},} & {{Eq}\mspace{14mu}(3)}\end{matrix}$where Detected_Set denotes a set of detected CCs. The set of detectedCCs may include all or a subset of the M configured CCs. Detected CCsmay be determined as described above.

As shown in equation (3), when the detected CCs are known from thedetection of downlink grants, the ACK/NACK bitwidth may be determinedbased on the ACK/NACK bits for only the detected CCs. This may result ina smaller and more accurate ACK/NACK bitwidth.

n_(C) in equations (1) to (3) may be defined in the same manner ordifferent manners. For example, n_(C) in equation (1) may be determinedbased on a transmission mode of each CC in the configured set, whereasn_(C) in equation (3) may be determined based on a DCI format of adownlink grant for the CCs in the detected set.

For the second scheme with DAI indicating the number of scheduled CCs,the ACK/NACK bitwidth for M configured CCs may be determined differentlyfor the ordered and non-ordered cases described above. In one example ofthe non-ordered case, ACK/NACK bitwidth may be determined based on theconfigured CCs, as shown in equation (1). Although only a subset of theM configured CCs may be scheduled, the DAI may not indicate whichparticular downlink CCs are scheduled. Hence, the UE may determined anACK/NACK bitwidth based on a number of ACK/NACK bits for all Mconfigured CCs.

When ordered feedback is used with the second scheme, ACK/NACK bitwidthmay be determined in different manners. In one example, the ACK/NACKbitwidth may be determined as follows:

$\begin{matrix}{n_{HARQ} = \left\{ \begin{matrix}n_{C} & {{{for}\mspace{14mu}{DAI}} = 1} \\{{DAI}*{\max\left( n_{C} \right)}} & {{{for}\mspace{14mu} 1} < {DAI} < M} \\{\sum\limits_{C \in {{Configured}\_{Set}}}n_{C}} & {{{for}\mspace{14mu}{DAI}} = M}\end{matrix} \right.} & {{Eq}\mspace{14mu}(4)}\end{matrix}$

In equation (4), the ACK/NACK bitwidth varies according to the number ofscheduled CCs and may be equal to the number of ACK/NACK bits for the CCon which PDCCH is transmitted when one downlink CC is scheduled (withDAI=1). The ACK/NACK bitwidth may be equal to the total number ofACK/NACK bits for all M configured CCs if all configured CCs arescheduled (with DAI=M). The ACK/NACK bitwidth and may be equal to thenumber of scheduled CCs times the maximum number of ACK/NACK bits perscheduled CC if two to M−1 downlink CCs are scheduled. SinceDAI*max(n_(C)) may be larger than Σn_(C), n_(HARQ) may be limited toΣn_(C).

In another example, when ordered feedback is used with the secondscheme, the ACK/NACK bitwidth may be determined as follows:

$\begin{matrix}{\mspace{79mu}{n_{HARQ} = \left\{ \begin{matrix}n_{C} & {{{for}\mspace{14mu}{DAI}} = 1} \\{{DAI}*{\max\left( n_{C} \right)}} & {{{for}\mspace{14mu} 1} < {DAI} < M} \\{\sum\limits_{C \in {{Configured}\_{Set}}}n_{C}} & {{{for}\mspace{14mu}{DAI}} = M}\end{matrix} \right.}} & {{Eq}\mspace{14mu}(5)} \\{n_{X} = {{\max\left\{ {n_{1},\ldots\mspace{14mu},{\cdot n_{M - {DAI} + 1}}} \right\}} + {\max\left\{ {n_{2},\ldots\mspace{14mu},{\cdot n_{M - {DAI} + 2}}} \right\}} + \ldots + {\max\left\{ {n_{DAI},\ldots\mspace{14mu},{\cdot n_{M}}} \right\}}}} & {{Eq}\mspace{14mu}(6)}\end{matrix}$

In equation (6), for a given DAI value, the first scheduled CC is amongdownlink CCs 1 through M−DAI+1, the second scheduled CC is amongdownlink CCs 2 through M−DAI+2, and so on, and the last scheduled CC isamong downlink CCs DAI to M. This observation is exploited in equation(6) to possibly reduce the ACK/NACK bitwidth. Since n_(X) may be largerthan Σn_(C), n_(HARQ) may be limited to Σn_(C). For example, UE 120 xmay be configured with five downlink CCs associated with 1, 2, 1, 2 and1 ACK/NACK bits based on the transmission modes configured for thesedownlink CCs. In this example, Σn_(C) is equal to 7 bits. If fourdownlink CCs are scheduled and DAI=4, then n_(X) is equal to 8 and islarger than Σn_(C). In this case, n_(HARQ) may be limited to 7.Conversely, if three downlink CCs are scheduled and DAI=3, then n_(X) isequal to 6 and is smaller than Σn_(C). In this case, n_(HARQ) is equalto 6. For the case of two downlink CCs, n_(HARQ) may be set to Σn_(C).

For the third scheme in which a DAI identifies both the number andidentity of the scheduled CCs, the ACK/NACK bitwidth for M configuredCCs may be determined as follows:

$\begin{matrix}{{n_{HARQ} = {\sum\limits_{C \in {{Scheduled}\_{Set}}}n_{C}}},} & {{Eq}\mspace{14mu}(7)}\end{matrix}$where Scheduled_Set denotes a set of scheduled CCs.

As shown in equation (7), when the scheduled CCs are known from the DAI,the ACK/NACK bitwidth may be determined based on the ACK/NACK bits foronly the scheduled CCs. For example, the number of ACK/NACK bits foreach scheduled CC may be determined based on (i) the transmission modeconfigured for the scheduled CC or (ii) the DCI format of a downlinkgrant for the scheduled CC. This would increase efficiency byfacilitating a more accurate determination of the ACK/NACK bitwidth.

Table 4 summarizes the determination of ACK/NACK bitwidth for the threeschemes listed in Table 3.

TABLE 4 ACK/NACK Bitwidth Determination Scheme Non-ordered Case OrderedCase Comments No DAI Σn_(C) over Same as non- Fixed ACK/NACK configuredCCs ordered case overhead if sum over or detected CCs configured CCs.DAI Σn_(C) over Equation (4) or Ordered ACK/NACK indicates configuredCCs Equations feedback may be more number of (5) & (6) efficient.scheduled CCs DAI Σn_(C) over Same as non- Minimum ACK/NACK identifiesscheduled CCs ordered case overhead. scheduled CCs

In one example of operation, which may be applicable for all threeschemes listed in Table 3, UE 120 x may determine the total number oftransport blocks received on the M configured CC. UE 120 x may detectfor downlink grants intended for UE 120 x and may determine the DCIformat of each detected downlink grant. UE 120 x may receive onetransport block on each downlink CC associated with a downlink granthaving a DCI format supporting one transport block. UE 120 x may receivetwo transport blocks on each downlink CC associated with a downlinkgrant having a DCI format supporting two transport blocks. UE 120 x maydetermine the total number of transport blocks received on allconfigured CCs as follows:

$\begin{matrix}{{n_{TB} = {\sum\limits_{C \in {{Detected}\_{Set}}}n_{{TB},C}}},} & {{Eq}\mspace{14mu}(8)}\end{matrix}$where n_(TB,C) is the number of transport blocks received on downlink CCC, and

n_(TB) is the total number of transport blocks received on allconfigured CCs.

The total number of transport blocks received on all configured CCs(n_(TB)) may be referred to as a total transport block count. UE 120 xmay determine the ACK/NACK bitwidth based on the total transport blockcount, e.g., one ACK/NACK bit for each received transport block, so thatn_(HARQ)=n_(TB). The number of transport blocks received on eachdownlink CC may be equal to or less than the number of transport blocksfor a transmission mode configured for that downlink CC. Hence, thetotal transport block count determined based on detected downlink grantsmay be equal to or less than the ACK/NACK bitwidth determined based ontransmission modes of the configured CCs or detected CCs. The ACK/NACKbitwidth determined based on transmission modes may be considered as (i)the maximum possible number of ACK/NACK bits for M configured CCs, or(ii) the total number of bits available to send ACK/NACK information forthe M configured CCs. The total transport block count may be consideredas the actual number of ACK/NACK bits to send for the M configured CCs.

UE 120 x may send ACK/NACK information for M configured CCs on eitherthe PUCCH or PUSCH in a given subframe, e.g., depending on whether UE120 x is also scheduled for data transmission on the uplink in thesubframe. The ACK/NACK bitwidth and/or the total transport block countmay be used for various purposes such as one or more of the following:

-   -   Power control of ACK/NACK information sent on the PUCCH,    -   Determination of a number of resource elements for sending        ACK/NACK information on the PUSCH,    -   Determination of an ACK/NACK feedback scheme for sending        ACK/NACK information on the PUCCH,    -   Determination of a code rate and/or a coding scheme for sending        ACK/NACK information on the PUCCH or PUSCH, and    -   Determination of available bits for sending CSI and/or other        information with ACK/NACK information on the PUCCH or PUSCH.

A multi-carrier UE may also perform power control for the PUCCH based onthe ACK/NACK bitwidth or the total transport block count. In general,the signal-to-noise ratio (SNR) needed to reliably receive an ACK/NACKtransmission may be dependent on the ACK/NACK bitwidth, or the number ofACK/NACK bits to send. The ACK/NACK bitwidth may, in turn, be dependenton the number of scheduled CCs. Since the required SNR may vary by morethan 3 dB, e.g., for one scheduled CC versus five scheduled CCs,accurate determination of ACK/NACK bitwidth is important for efficientoperation in a multi-carrier network.

The transmit power to use to send ACK/NACK information and possibly CSIon the PUCCH may be determined as follows:P _(PUCCH) =f{h(n _(CSI) ,n _(HARQ))},  Eq (9)where

n_(CSI) is the number of CSI bits to send with ACK/NACK information,

h(·) is a predefined function described in LTE,

f(·) is another predefined function described in LTE, and

P_(PUCCH) is the transmit power for the PUCCH.

As shown in equation (9), the transmit power of the PUCCH may bedependent on the number of ACK/NACK bits to send, or ACK/NACK bitwidth.The ACK/NACK bitwidth for power control of the PUCCH may be determinedin various manners. In a first example, which may be referred to as aslow option, ACK/NACK bitwidth may be determined based on the configuredCCs for UE 120 x, which may be computed as shown in equation (1) for thefirst scheme. In a second example, which may be referred to as a mediumoption, the ACK/NACK bitwidth may be determined based on the activatedCCs for UE 120 x, which may be computed as shown in equation (2) for thefirst scheme. In a third example, which may be referred to as a fastoption, the ACK/NACK bitwidth may be determined based on the detectedCCs carrying data on the PDSCH, which may be computed as shown inequation (3) for the first scheme.

Other approaches may also include determining ACK/NACK bitwidth based onthe scheduled CCs. For example, ACK/NACK bitwidth may be determined overthe set of scheduled CCs as when the DAI identifies both number andidentity of each scheduled CC, e.g., as shown in equation (7).Alternatively, the ACK/NACK bitwidth may be determined based on thetotal number of transport blocks received on the M configured CCs, e.g.,as shown in equation (8). The ACK/NACK bitwidth may also be depend uponwhether an ordered or non-order feedback configuration is utilized aspreviously discussed.

The slow and medium options may result in “over” power control since UE120 x may be scheduled on fewer downlink CCs than the configured CCs. UE120 x may then use higher transmit power for the PUCCH than necessary.The fast option may result in “under” power control since UE 120 x maymiss detecting downlink grants on the PDCCH for some scheduled CCs. UE120 x may then use less transmit power for the PUCCH than necessary.However, the likelihood of missing detection of downlink grants may below (e.g., typically around 1% for each downlink CC). Hence, the underpower control issue may not be severe.

Power control of the PUCCH can be performed by eNB 110 x to mitigate thepotential for a power control mismatch as described above. For the slowand medium options, eNB 110 x may determine a power down command basedon the difference between the number of scheduled CCs and the number ofconfigured or activated CCs. For the fast option, eNB 110 x maydetermine a power up command based on the difference between an estimateof the number of detected CCs by UE 120 x (which is unknown to eNB 110x) and the number of scheduled CCs (which is known to eNB 110 x). Forall options, eNB 110 x may send a power control command (which may be apower down command or a power up command) to UE 120 x. The power controlcommand may be sent via embedded information in a downlink grant, or viagroup power control in DCI formats 3/3A, or via some other mechanism. UE120 x may adjust its computed transmit power for the PUCCH based on thepower control command.

For transmissions on PUSCH, the number of resource elements to use tosend ACK/NACK information (which may be referred to as the requirednumber of PUSCH resource elements) may be determined based on theACK/NACK bitwidth or the total transport block count. In one example, UE120 x may determine a number of PUSCH resource elements based on theACK/NACK bitwidth for the configured CCs, which may be computed as shownin equation (1) for the no-DAI case. In a second example, UE 120 x maydetermine the number of PUSCH resource elements for acknowledging a datatransmission based on the ACK/NACK bitwidth for the activated CCs, whichmay be computed as shown in equation (2) for the no-DAI case. In a thirdexample, UE 120 x may determine the number of PUSCH resource elementsbased on the ACK/NACK bitwidth for the detected CCs, which may becomputed as shown in equation (3) for the no-DAI case. In otherexamples, UE 120 x may determine the number of PUSCH resource elementsbased on (i) the ACK/NACK bitwidth for the scheduled CCs, which may bedetermined as shown in equation (7) for the third scheme, or (ii) thetotal number of transport blocks received on the M configured CCs, whichmay be determined as shown in equation (8).

In each of the above examples, the number of PUSCH resource elements foracknowledging a data transmission may be reserved or set aside fromamong all resource elements available on the PUSCH. UE 120 x may sendACK/NACK information on the reserved resource elements on the PUSCH.Data and/or other information may be sent on the remaining resourceelements on the PUSCH. eNB 110 x may configure UE 120 x for a particularresource utilization scheme on the PUSCH to avoid misalignment.

When UE 120 x determines that ACK/NACK information is sent on the PUCCH,ACK/NACK feedback scheme may be determined based on the ACK/NACKbitwidth or the total transport block count. For example, up to two bitsof ACK/NACK information may be sent on the PUCCH based on PUCCH format 1a or 1 b. PUCCH format 1 a supports transmission of one ACK/NACK bit onthe PUCCH and may be used when one downlink CC is scheduled. PUCCHformat 1 b supports transmission of two ACK/NACK bits on the PUCCH andmay be used when two transport blocks are scheduled on one downlink CCor one transport block is scheduled on each of two downlink CCs.

Up to four bits of ACK/NACK information may be sent on the PUCCH basedon PUCCH format 1 b and channel selection. In this example, twosignaling bits, b₀ and b₁, may be sent on one of multiple PUCCHresources available for use by UE 120 x. The values of bits b₀ and b₁ aswell as the selected PUCCH resource may be determined based on theACK/NACK information.

When UE 120 x is configured for PUCCH format 3, which utilizesDFT-spread OFDM (DFT-S-OFDM), more than four bits of ACK/NACKinformation may be sent on the PUCCH. For PUCCH format 3, n_(HARQ) bitsof ACK/NACK information may be transformed to the frequency domain basedon a DFT and mapped to resource elements in one or more resource blocksused for ACK/NACK transmission. SC-FDMA symbols may be generated basedon the mapped symbols.

PUCCH format 3 may be used to send ACK/NACK information regardless ofthe number of downlink CCs. This approach allows the same PUCCH formatto be used irrespective of the number of configured CCs or scheduledCCs. For example, eNB 110 x may process the ACK/NACK information basedon one PUCCH format (instead of having to perform blind detection fordifferent PUCCH formats). Additionally, using the additional payloadavailable with PUCCH format 3, UE 120 x can multiplex CSI and/or otherinformation with ACK/NACK information. PUCCH format 3 may also be usedto send only CSI, which may simplify operation of eNB 110 x to detectfor CSI and/or ACK/NACK information from UE 120 x.

All or a subset of the designs described above may be used to sendACK/NACK information on the PUCCH. For example, PUCCH format 1 a/1 b andPUCCH format 3 may be used as appropriate. The ACK/NACK bitwidth forselecting a suitable ACK/NACK feedback scheme may be determined based onthe configured CCs, the activated CCs, the detected CCs, or thescheduled CCs.

UE 120 x can select a code rate and/or a coding scheme for ACK/NACKinformation based on the ACK/NACK bitwidth or the total transport blockcount. The ACK/NACK information may be encoded based on a block code(e.g., a Reed-Muller code) of a particular code rate to obtain codeddata. The coded data may be further processed and sent on the PUCCH orPUSCH. Selection of a suitable code rate may be especially relevant forACK/NACK information sent on the PUCCH based on PUCCH format 3 as wellas for ACK/NACK information multiplexed with data on the PUSCH.

As described above, the number of bits of ACK/NACK information(n_(HARQ)) may be variable and dependent on the ACK/NACK bitwidth. Thenumber of bits of coded data (n_(PAYLOAD)), on the other hand, may befixed and dependent on the available payload for ACK/NACK information onthe PUCCH or PUSCH. The code rate may be selected based on n_(HARQ) andn_(PAYLOAD) so that the coded data can be sent in the available payloadon the PUCCH or PUSCH. The code rate may be determined based on theACK/NACK bitwidth for the configured CCs, the activated CCs, thedetected CCs, or the scheduled CCs. Selecting the code rate based on theACK/NACK bitwidth for the configured CCs may ensure that eNB 110 x andUE 120 x will both use the same code rate. Selecting the code rate basedon the ACK/NACK bitwidth for the activated CCs or the detected CCs mayprovide better performance with an increased possibility of misalignmentbetween the code rate determined by eNB 110 x and the code ratedetermined by UE 120 x. In one example, eNB 110 x performs decoding fordifferent possible code rates to address possible misalignments. Fastadaptation based on the detected CCs may enable the use of differentbasis sequences for the block code.

The number of bits available to send CSI and/or other information mayalso be determined based on the ACK/NACK bitwidth or the total transportblock count. ACK/NACK information, CSI, and/or other information may bemultiplexed, and the resultant UCI may be sent on the PUCCH or PUSCH.One PUCCH or one PUSCH can support feedback of both ACK/NACK informationand CSI simultaneously, which may be jointly encoded. The availablepayload for UCI on the PUCCH or PUSCH may be fixed and may be denoted asn_(PAYLOAD). For example, up to 13 information bits may be sent on thePUCCH based on PUCCH format 3.

In one example, the number of bits available to send CSI and/or otherinformation, n_(CSI), is determined based on the ACK/NACK bitwidth orthe total transport block count, as follows:n _(CSI) =n _(PAYLOAD) −n _(HARQ).  Eq (10)

n_(HARQ) in equation (10) may be determined based on the ACK/NACKbitwidth for the configured CCs, the activated CCs, or the detected CCs,or the scheduled CCs. n_(HARQ) in equation (10) may also be determinedbased on the total transport block count. n_(HARQ) may be determinedbased on the DAI, if available. n_(HARQ) may also be dependent onwhether the ACK/NACK information is ordered or not ordered.

eNB 110 x may control the number of ACK/NACK bits in view of potentialfeedback overhead for CSI. For example, eNB 110 x may schedule up tofive downlink CCs in a subframe if there is only 4-bit wideband CSIfeedback to report with the ACK/NACK information. Similarly, eNB 110 xmay schedule one or two downlink CCs with 2-bit ACK/NACK feedback in aparticular subframe when 11-bit CSI feedback is expected and would bemultiplexed with the ACK/NACK information. eNB 110 x may thus schedule anumber of downlink CCs such that the total overhead for ACK/NACKfeedback and CSI feedback can fit in the available payload for UCI.

Table 5 lists four exemplary designs of sending ACK/NACK information.Each of the four ACK/NACK designs is described in further detail below.

TABLE 5 ACK/NACK Designs ACK/NACK Design Description First No DAI No DAIfor downlink CCs. Design CSI not multiplexed with ACK/NACK. Second NoDAI No DAI for downlink CCs. Design CSI can be multiplexed withACK/NACK. Third DAI indicates DAI indicates number of downlink CCsDesign number of scheduled in a subframe. scheduled CCs CSI can bemultiplexed with ACK/NACK. Fourth DAI identifies DAI indicates number ofdownlink CCs and Design scheduled CCs identifies the scheduled CCs in asubframe. CSI can be multiplexed with ACK/NACK.

In the first ACK/NACK design, DAI is not used for downlink CCs (but maybe used for downlink subframes in TDD as described below). The ACK/NACKbitwidth or the total transport block count for power control of thePUCCH carrying ACK/NACK information may be determined based on detectedCCs, e.g., as shown in equation (3) or (8). The ACK/NACK bitwidth or thetotal transport block count for determining the number of resourceelements for sending ACK/NACK information on the PUSCH may be determinedbased on configured CCs, e.g., as shown in equation (1). When DAI is notavailable, UE 120 x may be configured to drop CSI when it collides withACK/NACK information in a subframe and the ACK/NACK informationcomprises more than two bits. In particular, UE 120 x may not multiplexCSI with ACK/NACK information when DAI is not available and itdetermines that there are more than two bits of ACK/NACK feedback. Ifthere is only one or two ACK/NACK bits, then ACK/NACK information may bemultiplexed with CSI as described in LTE Release 8.

In situations where DAI is not utilized, it is possible to reduce DCIoverhead. However, without the additional information about scheduledCCs, there may be errors in determining the ACK/NACK bitwidth, which mayresult in some errors in determination of transmit power for the PUCCHor the number of resource elements in the PUSCH to send ACK/NACKinformation. Determining the ACK/NACK bitwidth based on the detected CCsfor PUCCH power control and based on the configured CCs for countingresource elements on the PUSCH as described herein may mitigate theimpact of such errors.

The second ACK/NACK design also does not utilize DAI but provides formultiplexing ACK/NACK with CSI on the PUCCH or PUSCH. The ACK/NACKbitwidth or the total transport block count for ascertaining the numberof bits available to send CSI and/or other information may be determinedbased on the configured CCs, the activated CCs, or the detected CCs.Allowing CSI to be multiplexed with ACK/NACK information may result inless frequent dropping of CSI, which may improve performance of datatransmission.

In the third ACK/NACK design, a DAI may be included in a downlink grantand may indicate the number of downlink CCs scheduled in a subframe,i.e., the total number of PDSCH transmissions. UE 120 x may performvarious functions based on the DAI. For example, UE 120 x may determinethe ACK/NACK bitwidth based on the DAI, as shown in equation (4) or (5).UE 120 x may then determine the transmit power for sending ACK/NACKinformation on the PUCCH, the number of resource elements for sendingACK/NACK information on the PUSCH, the ACK/NACK feedback scheme forsending ACK/NACK information, the number of bits available to send CSIand/or other information, the code rate for encoding ACK/NACKinformation, etc. based on the ACK/NACK bitwidth or the total transportblock count. UE 120 x may also utilize the DAI to reduce PDCCH blinddetection and lower the associated probability of false alarms. Inparticular, UE 120 x may utilize explicit information on the number ofscheduled CCs obtained from the DAI to determine when to stop decodingthe PDCCH and avoid processing downlink CCs that do not include anydownlink grants.

In the fourth ACK/NACK design, a DAI may be included in a downlink grantand may indicate both the number of downlink CCs scheduled in a subframeand the identify the scheduled CCs, i.e., the total number and positionof the scheduled CCs. CC identity may be signaled, for example, when thebits of the DAI correspond to different ones of the CCs configured forUE 120 x. Using information from the DAI, UE 120 x may perform variousfunctions. For example, UE 120 x may accurately determine the ACK/NACKbitwidth based on the scheduled CCs indicated by the DAI, as shown inequation (7). UE 120 x may also accurately determine the transmit powerfor sending ACK/NACK information on the PUCCH, the number of resourceelements for sending ACK/NACK information on the PUSCH, the ACK/NACKfeedback scheme for sending ACK/NACK information, the number of bitsavailable to send CSI and/or other information, the code rate forencoding ACK/NACK information, etc. based on the ACK/NACK bitwidth orthe total transport block count. UE 120 x may also utilize the DAI todetermine which downlink CCs to decode the PDCCH for downlink grants andwhich downlink CCs to skip.

Table 6 summarizes transmission of ACK/NACK information on the PUCCH forthe three schemes listed in Table 3.

TABLE 6 ACK/NACK Transmission on PUCCH Scheme Description No DAI PUCCHpower control based on detected CCs. DAI indicates PUCCH power controlbased on DAI. number of Some leftover room for multiplexing CSI withscheduled CCs ACK/NACK. Improved PDCCH blind detection and false alarmprobability. DAI identifies PUCCH power control based on DAI. scheduledCCs Accurate ACK/NACK bitwidth determination. Maximum leftover room formultiplexing CSI with ACK/NACK. Improved PDCCH blind detection and falsealarm probability.

Table 7 summarizes transmission of ACK/NACK information on the PUSCH forthe three schemes listed in Table 3.

TABLE 7 ACK/NACK Transmission on PUSCH Scheme Description No DAI Numberof resource elements for ACK/NACK information determined based onconfigured CCs or activated CCs. DAI Number of resource elements forACK/NACK information indicates determined based on DAI. number ofImproved PDCCH blind detection and false alarm probability. scheduledCCs DAI Number of resource elements for ACK/NACK information identifiesdetermined based on DAI. scheduled Accurate ACK/NACK bitwidthdetermination. CCs Improved PDCCH blind detection and false alarmprobability.

UE 120 x may be configured with semi-persistent scheduling (SPS) on thedownlink. For SPS, UE 120 x may be semi-statically configured withpertinent parameters for data transmission on a downlink CC, and eachPDSCH transmission may occur without sending a downlink grant on thePDCCH. SPS may be supported on only the downlink PCC or on any downlinkCC configured for UE 120 x.

When SPS is present (possibly on only the downlink PCC), misalignmentbetween eNB 110 x and UE 120 x may occur even if a DAI is present indownlink grants sent on downlink SCCs. For example, UE 120 x may beconfigured with two downlink CCs, with CC1 being a PCC and CC2 being anSCC. UE 120 x may be configured for SPS on the PCC without DAI and maybe dynamically scheduled on the SCC with DAI. If UE 120 x fails todetect the PDCCH for CC2, it may not know whether there is (i) only anSPS transmission on CC1, or (ii) both an SPS transmission on CC1 and adynamically scheduled transmission on CC2, or (iii) dynamicallyscheduled transmissions on both CC1 and CC2 (with the dynamicallyscheduled transmission on CC1 superseding an SPS transmission).

The situation described above may be addressed in various manners. Inone example, UE 120 x may behave as if the DAI is not included indownlink grants. UE 120 x may then perform PUCCH power control based ondetected CCs, determine the number of PUSCH resource elements based onconfigured CCs, etc. In another example, the DAI may include informationfor the PCC regardless of whether an SPS transmission or a dynamicallyscheduled transmission is sent on the PCC. In yet another example, theDAI may exclude information for the PCC if it has an SPS transmissionand may include information for the PCC if it has a dynamicallyscheduled transmission. An SPS transmission on the PCC may be associatedwith a fixed bitwidth (e.g., 1 bit) and a fixed location on the PUCCH orPUSCH if there is no dynamic scheduling transmission on the PCC.Otherwise, the DAI may include information for the PCC if it has adynamically scheduled transmission. Dynamically scheduled transmissionmay supersede SPS transmission when they conflict. In each case, UE 120x may perform PUCCH power control, determine the number of PUSCHresource elements, etc., as described above based on the availability ofthe DAI (or lack thereof).

In the third scheme shown in Table 3, a DAI may be included in eachdownlink grant and may identify all scheduled CCs. This arrangement isshown in FIG. 7. With information from the DAI, UE 120 x may obtainknowledge of the scheduled CCs as long as at least one downlink grant isreceived in a particular subframe. UE 120 x may determine the ACK/NACKbitwidth based on the number of ACK/NACK bits for each scheduled CC,e.g., as shown in equation (7).

It may be desirable for UE 120 x to send DTX to indicate a downlinkgrant/PDCCH that is not detected by UE 120 x. For example, UE 120 x maydetermine that CCx is scheduled based on the DAI included with adownlink grant received on CCy. However, UE 120 x may not detect adownlink grant for a PDSCH transmission on CCx. In that case, dependingupon its configuration, UE 120 x signals DTX for CCx, and eNB 110 x mayuse the DTX feedback to improve transmission of the PDCCH for CCx.

Unused bits may be used to convey DTX as follows. A given downlink CC,CCj, may be configured with a transmission mode supporting two transportblocks (e.g., a MIMO mode) and may be associated with two ACK/NACK bits.However, in a particular subframe, CCj may be scheduled with atransmission of one transport block (e.g., a SIMO mode). Only oneACK/NACK bit may needed to acknowledge the transmission on CCj. Theunused bit allocated based on the transmission mode may be used toconvey whether or not there is a missing downlink grant/PDCCH based uponinformation from the DAI. Unused bits may also be referred to asleftover bits, orphan bits, etc. Unused bits for multiple downlink CCsmay be used jointly to convey more information to eNB 110 x, e.g., toconvey which particular downlink grant/PDCCH is not detected by UE 120x.

In one example of reusing ACK/NACK bits, UE 120 x may be configured withthree downlink CCs, which may include CC1, CC2 and CC3. All threeconfigured CCs may be associated with transmission modes supporting twotransport blocks, for which two ACK/NACK bits are potentially needed foracknowledging a corresponding PDSCH transmission. eNB 110 x may scheduletwo of the configured CCs in a given subframe, with CC1 being scheduledwith DCI format 1A for one transport block, and CC3 being scheduled withDCI format 2 for two transport blocks. Four ACK/NACK bits may beavailable for the two scheduled CCs based on their transmission modes.However, for the data transmission described above, only three ACK/NACKbits may be generated, or one ACK/NACK bit for CC1 and two ACK/NACK bitsfor CC3. In that case, one unused bit would be available to UE 120 x forconveying DTX for one CC. The unused bit may, for example, be used toconvey DTX for CC3 and may be set to a first value (e.g., ‘0’) if adownlink grant/PUCCH for CC3 is received, or to a second value (e.g.,‘1’) if the downlink grant/PUCCH for CC3 is not received based oninformation about scheduled CCs obtained from the DAI. The four ACK/NACKbits may then be sent as follows:

-   -   Send {x100} to inform eNB 110 x that the downlink grant for CC3        is missing, or    -   Send {x0yz} to inform eNB 110 x that the downlink grant for CC3        is detected,        where x is an ACK/NACK bit for CC1, y and z are two ACK/NACK        bits for CC3, and x, y and z may each have a value of ‘0’ or        ‘1’.

In general, 12 bits may be used to convey ACK, NACK, or DTX for fivedownlink CCs. UE 120 x may be configured to report DTX whenever unusedbits are available, or to report DTX upon the occurrence or certainconditions. For example, UE 120 x may report DTX only if the number ofconfigured or scheduled CCs is less than four (in order to fit into a10-bit ACK/NACK payload), or only if two downlink CCs are configured,etc.

A DAI may also be used to convey information about scheduled subframesin TDD. For example, 2-bit DAI may be included in a downlink grant sentbased on DCI format 1, 1A, 1B, 1D, 2, 2A or 2B in LTE. The 2-bit DAI maybe sent in subframe n and may indicate the accumulative number ofPDCCH(s) with assigned PDSCH transmission(s) and PDCCH indicating SPSrelease, up to the present subframe within subframe(s) n-k, with kbelonging to K, where K denotes a set of downlink subframes associatedwith the same uplink subframe in which ACK/NACK feedback is sent. The2-bit DAI may also be included in an uplink grant sent based on DCIformat 0 in LTE. In this case, the DAI may be detected by UE 120 x insubframe n-k′ and may represent the total number of subframes with PDSCHtransmissions and with PDCCH indicating downlink SPS release withinsubframes n-k′, with k′ belonging to K. In each case, the DAI may helpUE 120 x to detect the missing downlink grants, facilitate moreefficient ACK/NACK feedback, and provide other advantages.

In one design, a two-dimensional (2-D) DAI may be used to conveyinformation about scheduled CCs and scheduled subframes formulti-carrier operation in TDD. The 2-D DAI may include two components,DAI_Time and DAI_Freq, to cover time domain and frequency domain,respectively. DAI_Time may be included in a grant when operating in TDD.DAI_Freq may be included in a grant if UE 120 x is configured with twoor more downlink CCs in either FDD or TDD. DAI_Time may comprise twobits and may be provided for each downlink CC. DAI_Time may be includedin a downlink grant or an uplink grant and may indicate the accumulativenumber of PDSCH transmissions (in time) over downlink subframes in adownlink subframe association set on a particular downlink CC. DAI_Freqmay comprise one to three bits and may be provided for each downlinksubframe. DAI_Freq may be included in a downlink grant or an uplinkgrant and may indicate the total number of scheduled CCs and/or whichCCs are scheduled in a given subframe. DAI_Time and/or DAI_Freq may alsoconvey different information dependent on whether they are included in adownlink grant or an uplink grant. For example, DAI_Freq included in adownlink grant may identify the scheduled CCs whereas DAI_Freq includedin an uplink grant may indicate the number of scheduled CCs.

In some situations, it is desirable to reduce the number of ACK/NACKbits for transmission on the uplink. The number of bits of ACK/NACKinformation may be reduced by performing spatial bundling, subframebundling, and/or CC bundling, as described in Table 8.

TABLE 8 Bundling Bundling Type Description Spatial Bundle ACKs and/orNACKs for transport blocks received via Bundling multiple layers on onedownlink CC in one subframe. Subframe Bundle ACKs and/or NACKs fortransport blocks received Bundling on one downlink CC in multiplesubframes. CC Bundle ACKs and/or NACKs for transport blocks received onBundling multiple downlink CCs in one subframe.

In general, a UE may utilize one or more types of bundling to reduce theamount of ACK/NACK feedback. Bundling may be performed in differentmanners depending on various factors such as whether a wireless networkutilizes FDD or TDD, the number of configured CCs, the uplink-downlinkconfiguration in TDD, the desired ACK/NACK payload size, channelconditions, etc.

For spatial bundling, multiple transport blocks may be received viamultiple layers on one downlink CC in one subframe, and an ACK or a NACKmay be obtained for each transport block. A bundled ACK may be generatedif ACKs are obtained for all transport blocks. A bundled NACK may begenerated if a NACK is obtained for any transport block. For subframebundling, multiple transport blocks may be received on one downlink CCin multiple subframes, e.g., one transport block in each subframe. AnACK or a NACK may be obtained for each transport block. A bundled ACKmay be generated if ACKs are obtained for all transport blocks, and abundled NACK may be generated if a NACK is obtained for any transportblock. For CC bundling, multiple transport blocks may be received onmultiple downlink CCs in one subframe, e.g., one transport block oneeach downlink CC. An ACK or a NACK may be obtained for each transportblock. A bundled ACK may be generated if ACKs are obtained for alltransport blocks, and a bundled NACK may be generated if a NACK isobtained for any transport block. With all three types of bundling, wheneNB 110 x receives a bundled NACK, it may retransmit all of theapplicable transport blocks.

In some examples, spatial bundling is utilized with multi-carrieroperation in FDD. Up to M ACK/NACK bits may be generated for Mconfigured CCs, e.g., one ACK/NACK bit for each configured CC orscheduled CC. To improve coverage of ACK/NACK transmission, the numberof configured CCs may be limited and/or ACK/NACK information may be sentwith repetition, e.g., by a factor of 2, 4, or 6. ACK/NACK repetitionmay be utilized when there is little impact to UCI transmission. Forexample, since a CSI transmission may be dropped when an ACK/NACKtransmission is sent, ACK/NACK repetition may be utilized when CSItransmission is not impacted.

In some examples, spatial bundling and subframe bundling may utilizedfor multi-carrier operation in TDD. UE 120 x may be configured with (i)up to five downlink CCs for multi-carrier operation and (ii) anuplink-downlink configuration with up to four downlink subframes to oneuplink subframe for TDD. One or more ACK/NACK feedback modes may besupported, and each ACK/NACK feedback mode may perform bundling in adifferent manner.

In a first ACK/NACK feedback mode for multi-carrier operation in TDD,only one type of bundling may be performed, with the bundling type beingdependent on the number of configured CCs. If one CC is configured, thenonly spatial bundling may be performed to obtain up to four ACK/NACKbits, one ACK/NACK bit for each downlink subframe. If two CCs areconfigured, then only subframe bundling may be performed to obtain up tofour ACK/NACK bits, or up to two ACK/NACK bits for each configured CC orscheduled CC. Alternatively, only spatial bundling may be performed toobtain up to eight ACK/NACK bits, or one ACK/NACK bit for eachconfigured CC in each downlink subframe. If three or more CCs areconfigured, then only subframe bundling may be performed to obtain up to2*M ACK/NACK bits, or up to two ACK/NACK bits for each configured CC orscheduled CC.

In a second ACK/NACK feedback mode for multi-carrier operation in TDD,one or more types of bundling may be performed, with the bundlingtype(s) being dependent on the number of configured CCs. If one CC isconfigured, then only subframe bundling may be performed to obtain up totwo ACK/NACK bits. If two CCs are configured, then both spatial bundlingand subframe bundling may be performed to obtain up to two ACK/NACKbits. If three or more CCs are configured, then both spatial bundlingand subframe bundling may be performed to obtain up to M ACK/NACK bits,e.g., one ACK/NACK bit for each configured CC or scheduled CC.

Bundling may also be performed in other manners. For example, CCbundling may be performed for a subset of the M configured CCs (e.g.,downlink CCs with sufficient correlation) instead of all M configuredCCs. Subframe bundling may be performed for a subset of all downlinksubframes in a radio frame.

The techniques described herein provide various advantages. First, thetechniques may facilitate efficient ACK/NACK feedback for multi-carrieroperation in FDD and TDD. The techniques may also provide multiplexingcapability among different types of UCI, e.g., multiplexing of ACK/NACKand CSI in one subframe. A DAI may cover time domain (for TDD) and/orfrequency domain (for FDD). A DAI may also be defined to be causal, sothat a DAI sent in subframe n does not cover scheduling in subframes n+1and later. This may allow independent scheduling to be maintained acrossdownlink subframes in a bundling window.

FIG. 8 shows an exemplary process 800 for sending ACK/NACK informationin a multi-carrier wireless network. Process 800 may be performed by aUE (as described below) or by some other entity. The UE may receive agrant on a CC in a plurality of CCs configured for the UE (block 812).The plurality of configured CCs at block 812 may be downlink CCs in awireless network utilizing FDD, downlink CCs in wireless networkutilizing TDD, or a combination thereof.

The UE may be scheduled for a data transmission on at least onescheduled CC in the plurality of configured CCs. The UE may determinethe number of scheduled CCs and an identifier of each scheduled CC inthe data transmission based on the grant (block 814). The UE maydetermine ACK/NACK information for the data transmission based on thenumber of scheduled CCs and the identifier of each scheduled CC (block816). The UE may send the ACK/NACK information as feedback for the atleast one data transmission (block 818).

In one example, the UE may order ACK/NACK bits for the scheduled CCs inthe data transmission based on an index of each CC in the plurality ofconfigured CCs, e.g., as illustrated by the ordered case in FIG. 6. Inanother example, the UE may place ACK/NACK bit(s) for each CC at aspecific position assigned to that CC, e.g., as illustrated by thenon-ordered case in FIG. 6.

The UE may determine the number of scheduled CCs and the identifier ofeach scheduled CC by detecting a DAI in the grant. The DAI can providean explicit indication of which CCs are scheduled in a particularsubframe by the UE can determine a corresponding transmission mode, etc.The DAI may have a variable size, which may be determined by the basestation based on the number of CCs that are configured for the UE.Alternatively, the DAI may have a fixed size, which may be based on amaximum allowable number of configured CCs.

In one example, the UE may obtain a bitmap indicative of the number ofscheduled CCs and the identifier of each scheduled CC from the grantsuch as the arrangement shown in FIG. 7. The number of bits of thebitmap may be less than the number of configured CCs for the UE. Theplurality of configured CCs may include a first CC and at least oneremaining CC. The grant may be for a data transmission on the first CC,and the bitmap may identify each scheduled CC in the at least oneremaining CC.

The UE may determine a transmission mode of each scheduled CC based oninformation obtained from the DAI. The UE may determine a total numberof ACK/NACK bits for acknowledging the data transmission based on thetransmission mode of each scheduled CC and the number of scheduled CCs.For example, the UE may determine a number of ACK/NACK bits for eachscheduled CC individually according to it transmission mode. The UE maythen determine the total number of ACK/NACK bits for the datatransmission based on the number of ACK/NACK bits for each scheduled CC,e.g., as shown in equation (7).

The total number of ACK/NACK bits may be used for various purposes. Inone example, the UE may determine a transmit power for sending theACK/NACK information based on the total number of ACK/NACK bits. The UEmay send the ACK/NACK information on a PUCCH based on the determinedtransmit power. In another example, the UE may determine a number ofresource elements for sending the ACK/NACK information based on thetotal number of ACK/NACK bits. The UE may send the ACK/NACK informationon a PUSCH based on the determined number of resource elements.

The UE may determine a PUCCH format, a code rate, and/or a coding schemefor sending the ACK/NACK information based on the total number ofACK/NACK bits. For instance, the UE may select PUCCH format 1 b when thetotal number of ACK/NACK bits is below a threshold value and PUCCHformat 3 when the total exceeds the threshold. The UE may send theACK/NACK information on the PUCCH based on the determined PUCCH format,a code rate, and/or a coding scheme. The UE may also determine a numberof bits for sending CSI based on the total number of ACK/NACK bits andan available payload size. The UE may multiplex the CSI with theACK/NACK information based on the available bits for sending the CSI.

The UE may determine the number of transport blocks received on eachscheduled CC. For example, the UE may determine that (i) one transportblock is received on each scheduled CC associated with a downlink granthaving a DCI format supporting one transport block and (ii) twotransport blocks are received on each scheduled CC associated with adownlink grant having a DCI format supporting two transport blocks. TheUE may determine the total number of transport blocks received on the atleast one scheduled CC based on the number of transport blocks receivedon each scheduled CC.

The total number of transport blocks may be used for various purposes.In one design, the UE may determine a transmit power for sending theACK/NACK information based on the total number of transport blocksreceived in the data transmission. The UE may send the ACK/NACKinformation on a PUCCH based on the determined transmit power.Alternatively, when the ACK/NACK information is to be sent on PUSCH, theUE may determine the number of resource elements based on the totalnumber of transport blocks received in the data transmission. The UE maysend the ACK/NACK information on a PUSCH based on the determined numberof resource elements.

With TDD, the UE may determine a number of downlink subframes in whichthe UE is scheduled, e.g., based on the grant. The UE may determineACK/NACK information for data transmission received on the at least onescheduled CC in the determined number of downlink subframes. TheACK/NACK information may be determined based on the number of scheduledCCs, the identifier of each scheduled CC, and the number of downlinksubframes in which the UE is scheduled. Additionally, to reduce theamount of ACK/NACK feedback, the UE may perform spatial bundling,subframe bundling, CC bundling, or a combination thereof as previouslydescribed.

In one example, the UE may identify at least one unused bit based on (i)the number of bits available to send the ACK/NACK information and (ii)the number of bits to send for the ACK/NACK information. Based oninformation obtained from the DAI, the UE may send informationindicating that a grant is missed for one of the scheduled CCs using theat least one unused bit.

The grant received by the UE in block 812 may be a downlink grant for adata transmission on one of the at least one scheduled CC or an uplinkgrant for a data transmission on the uplink. In one example, the eNBsends the DAI in separate downlink and uplink grants to reduce thelikelihood that the it is missed by the UE. The uplink grant may conveythe number of scheduled CCs and the identifier of each scheduled CC forthe data transmission on the downlink. The UE may perform blind decodingfor PDCCHs carrying grants based on the number of scheduled CCs and theidentifier of each scheduled CC.

In one design, information indicative of the number of scheduled CCs andthe identifier of each scheduled CC may be sent on only a PCC for theUE, or only a subset of the configured CCs for the UE, or all scheduledCCs for the UE. The PCC may be one of the plurality of configured CCsfor the UE.

FIG. 9 shows an exemplary process 900 for receiving ACK/NACK informationin a wireless network. Process 900 may be performed by a basestation/eNB (as described below) or by some other entity. The basestation may generate a grant indicating a number of scheduled CCs and anidentifier of each scheduled CC for a data transmission to a UE (block912). The grant may comprise a bitmap or some other informationindicative of the number of CCs scheduled for the data transmission andthe identifier of each scheduled CC.

The base station may send the grant on one of a plurality of CCsconfigured for the UE (block 914). The base station may send the datatransmission on at least one scheduled CC to the UE (block 916) andreceive ACK/NACK information for the data transmission from the UE(block 918). The ACK/NACK information may be determined by the UE basedon the number of scheduled CCs and the identifier of each scheduled CC.

In one design, the ACK/NACK information may be sent by the UE on a PUCCHat a transmit power determined based on the total number of transportblocks received by the UE in the data transmission. In another design,the ACK/NACK information may be sent by the UE on a PUSCH. The basestation may determine a transmission mode of CC scheduled for the datatransmission and may determine the total number of ACK/NACK bits for thedata transmission based on its transmission mode and the number ofscheduled CCs. For example, the base station may determine the number ofresource elements for acknowledging the data transmission based on thetotal number of ACK/NACK bits. The base station may receive the ACK/NACKinformation on a PUSCH based on the determined number of resourceelements. Also, the base station may determine a number of bitsavailable for sending CSI based on the total number of ACK/NACK bits andan available payload size. The base station may demultiplex the CSI andthe ACK/NACK information the number of available bits.

In one design, the base station may schedule the UE for datatransmission in a subframe based on whether reporting of CSI is due fromthe UE in the subframe. The base station may determine the number ofbits of CSI to report by the UE in the subframe. The base station maydetermine the number of bits available to send ACK/NACK information bythe UE in the subframe. The base station may schedule the UE for datatransmission in the subframe based on the number of bits available tosend ACK/NACK information by the UE, as described above.

FIG. 10 shows a block diagram of a design of a base station/eNB 110 yand a UE 120 y, which may be one of the base stations/eNBs and one ofthe UEs in FIG. 1. Within base station 110 y, a module 1010 may generatePDCCH transmissions comprising downlink grants and/or other DCI for oneor more CCs on which UE 120 y is scheduled. A module 1012 may generatePDSCH transmissions comprising data for the scheduled CCs. A transmitter1014 may generate and transmit one or more downlink signals comprisingthe PDCCH and/or PDSCH transmissions. A receiver 1016 may receive andprocess uplink signals transmitted by UE 120 y and other UEs. A module1020 may determine transmission parameters (e.g., an ACK/NACK feedbackscheme, a code rate, etc.) for ACK/NACK information sent by UE 120 y fordata transmission sent by eNB 110 y. A module 1018 may process one ormore received signals in accordance with the ACK/NACK transmissionparameters to recover the ACK/NACK information sent by UE 120 y. Module1018 may also recover CSI and/or other information sent by UE 120 y.

A module 1022 may determine a multi-carrier configuration of UE 120 y,e.g., determine which CCs are configured for UE 120 y for the downlinkand uplink, and which CCs are downlink PCC and uplink PCC for UE 120 y.A module 1024 may determine the ACK/NACK bitwidth and/or the totaltransport block count for UE 120 y based on various factors such aswhether or not DAI is included in grants sent to UE 120 y, theconfigured CCs or scheduled CCs for UE 120 y, whether bundling isperformed, etc. A module 1026 may determine the number of resourceelements used by UE 120 y to send ACK/NACK information on the PUSCH. Thevarious modules within base station 110 y may operate as describedabove. A controller/processor 1028 may direct the operation of variousmodules within base station 110 y. A memory 1030 may store data andprogram codes for base station 110 y. A scheduler 1032 may schedule UEsfor data transmission.

Within UE 120 y, a receiver 1050 may receive and process downlinksignals from base station 110 y and other base stations. A module 1052may process (e.g., demodulate and decode) one or more received signalsto recover PDCCH transmissions sent to UE 120 y. A module 1054 mayprocess the received signal to recover PDSCH transmissions sent to UE120 y. A module 1058 may determine ACK/NACK information for receiveddata transmission. A module 1056 may determine transmission parametersfor sending the ACK/NACK information. Module 1058 may send the ACK/NACKinformation on the PUCCH or PUSCH in accordance with the ACK/NACKtransmission parameters. Module 1058 may also send CSI and/or otherinformation on the PUCCH or PUSCH. A transmitter 1060 may generate andtransmit one or more uplink signals comprising a PUCCH transmission or aPUSCH transmission.

A module 1068 may determine a multi-carrier configuration of UE 120 y,e.g., determine which CCs are configured for UE 120 y for the downlinkand uplink, and which CCs are downlink PCC and uplink PCC for UE 120 y.A module 1062 may determine the ACK/NACK bitwidth and/or the totaltransport block count for UE 120 y based on various factors such aswhether or not DAI is included in grants sent to UE 120 y, theconfigured CCs or scheduled CCs for UE 120 y, whether bundling isperformed, etc. A module 1064 may perform power control for the PUCCHbased on the ACK/NACK bitwidth and/or the total transport block count,e.g., determine the transmit power for sending the ACK/NACK informationon the PUCCH. A module 1066 may determine the number of resourceelements for sending the ACK/NACK information on the PUSCH. The variousmodules within UE 120 y may operate as described above. Acontroller/processor 1070 may direct the operation of various moduleswithin UE 120 y. A memory 1072 may store data and program codes for UE120 y.

The modules in FIG. 10 may comprise processors, electronic devices,hardware devices, electronic components, logical circuits, memories,software codes, firmware codes, etc., or any combination thereof.

FIG. 11 shows a block diagram of a design of a base station/eNB 110 zand a UE 120 z, which may be one of the base stations/eNBs and one ofthe UEs in FIG. 1. Base station 110 z may be equipped with T antennas1134 a through 1134 t, and UE 120 z may be equipped with R antennas 1152a through 1152 r, where in general T≧1 and R≧1.

At base station 110 z, a transmit processor 1120 may receive data from adata source 1112 for transmission on one or more downlink CCs to one ormore UEs, process (e.g., encode and modulate) the data for each UE basedon one or more modulation and coding schemes selected for that UE, andprovide data symbols for all UEs. Transmit processor 1120 may alsoprocess control information (e.g., for grants, DAI, configurationmessages, etc.) and provide control symbols. Processor 1120 may alsogenerate reference symbols for reference signals. A transmit (TX) MIMOprocessor 1130 may precode the data symbols, the control symbols, and/orthe reference symbols (if applicable) and may provide T output symbolstreams to T modulators (MOD) 1132 a through 1132 t. Each modulator 1132may process its output symbol stream (e.g., for OFDM, etc.) to obtain anoutput sample stream. Each modulator 1132 may further condition (e.g.,convert to analog, amplify, filter, and upconvert) its output samplestream to obtain a downlink signal. T downlink signals from modulators1132 a through 1132 t may be transmitted via T antennas 1134 a through1134 t, respectively.

At UE 120 z, antennas 1152 a through 1152 r may receive the downlinksignals from base station 110 z and/or other base stations and mayprovide received signals to demodulators (DEMODs) 1154 a through 1154 r,respectively. Each demodulator 1154 may condition (e.g., filter,amplify, downconvert, and digitize) its received signal to obtain inputsamples. Each demodulator 1154 may further process the input samples(e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1156may obtain received symbols from all R demodulators 1154 a through 1154r, perform MIMO detection on the received symbols, and provide detectedsymbols. A receive processor 1158 may process (e.g., demodulate anddecode) the detected symbols, provide decoded data for UE 120 z to adata sink 1160, and provide decoded control information to acontroller/processor 1180.

On the uplink, at UE 120 z, a transmit processor 1164 may receive andprocess data from a data source 1162 and control information (e.g.,ACK/NACK information, CSI, etc.) from controller/processor 1180.Processor 1164 may also generate reference symbols for one or morereference signals. The symbols from transmit processor 1164 may beprecoded by a TX MIMO processor 1166 if applicable, further processed bymodulators 1154 a through 1154 r (e.g., for SC-FDM, OFDM, etc.), andtransmitted to base station 110 z. At base station 110 z, the uplinksignals from UE 120 z and other UEs may be received by antennas 1134,processed by demodulators 1132, detected by a MIMO detector 1136 ifapplicable, and further processed by a receive processor 1138 to obtaindecoded data and control information sent by UE 120 z and other UEs.Processor 1138 may provide the decoded data to a data sink 1139 and thedecoded control information to controller/processor 1140.

Controllers/processors 1140 and 1180 may direct the operation at basestation 110 z and UE 120 z, respectively. Processor 1140 and/or otherprocessors and modules at base station 110 z may perform or directprocess 900 in FIG. 9 and/or other processes for the techniquesdescribed herein. Processor 1180 and/or other processors and modules atUE 120 z may perform or direct process 800 in FIG. 8 and/or otherprocesses for the techniques described herein. Memories 1142 and 1182may store data and program codes for base station 110 z and UE 120 z,respectively. A scheduler 1144 may schedule UEs for data transmission onthe downlink and/or uplink.

It will be recognized that information and signals may be representedusing any of a variety of different technologies and techniques. Forexample, data, instructions, commands, information, signals, bits,symbols, and chips that may be referenced throughout the abovedescription may be represented by voltages, currents, electromagneticwaves, magnetic fields or particles, optical fields or particles, or anycombination thereof.

Also, it will be appreciated that the various illustrative logicalblocks, modules, circuits, and algorithm steps described in connectionwith the disclosure herein may be implemented as electronic hardware,computer software, or combinations of both. To clearly illustrate thisinterchangeability of hardware and software, various illustrativecomponents, blocks, modules, circuits, and steps have been describedabove generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by ageneral purpose or special purpose computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code means in the form of instructions or datastructures and that can be accessed by a general-purpose orspecial-purpose computer, or a general-purpose or special-purposeprocessor. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), then the coaxial cable,fiber optic cable, twisted pair, or DSL are included in the definitionof medium. Disk and disc, as used herein, includes compact disc (CD),laser disc, optical disc, digital versatile disc (DVD), floppy disk andblu-ray disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers. Combinations of the aboveshould also be included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method for wireless communication, comprising:receiving a grant on a component carrier (CC) in a plurality of CCsconfigured for a user equipment (UE); determining, based on the grant, anumber of scheduled CCs and an identifier of each scheduled CC for theUE; and determining acknowledgement/negative acknowledgement (ACK/NACK)information for a data transmission based on the number of scheduled CCsand the identifier of each scheduled CC.
 2. The method of claim 1,further comprising: determining a number of ACK/NACK bits for eachscheduled CC based on a transmission mode of the scheduled CC or anumber of transport blocks received on the scheduled CC; and determininga total number of ACK/NACK bits for the data transmission based on thenumber of ACK/NACK bits for each scheduled CC.
 3. The method of claim 1,further comprising: determining a transmit power for sending theACK/NACK information based on a total number of ACK/NACK bits for thedata transmission; and sending the ACK/NACK information on a physicaluplink control channel (PUCCH) based on the determined transmit power.4. The method of claim 1, further comprising: determining a number ofresource elements for sending the ACK/NACK information based on a totalnumber of ACK/NACK bits for the data transmission; and sending theACK/NACK information on a physical uplink shared channel (PUSCH) basedon the number of resource elements.
 5. The method of claim 1, furthercomprising: determining a physical uplink control channel (PUCCH) formatfor sending the ACK/NACK information based on a total number of ACK/NACKbits for data transmission; and sending the ACK/NACK information on thePUCCH based on the PUCCH format.
 6. The method of claim 1, furthercomprising: determining available bits for sending channel stateinformation (CSI) based on a total number of ACK/NACK bits for the datatransmission and an available payload size; and multiplexing the CSIwith the ACK/NACK information based on a number of the available bits.7. The method of claim 1, further comprising: determining a number oftransport blocks received on each scheduled CC; and determining a totalnumber of transport blocks received in the data transmission based onthe number of transport blocks received on each scheduled CC.
 8. Themethod of claim 7, wherein the determining the number of transportblocks received on each scheduled CC comprises: determining that onetransport block is received on each scheduled CC associated with adownlink grant having a downlink control information (DCI) formatsupporting one transport block, and determining that two transportblocks are received on each scheduled CC associated with a downlinkgrant having a DCI format supporting two transport blocks.
 9. The methodof claim 1, further comprising: determining a transmit power for sendingthe ACK/NACK information based on a total number of transport blocksreceived in the data transmission; and sending the ACK/NACK informationon a physical uplink control channel (PUCCH) based on the determinedtransmit power.
 10. The method of claim 1, further comprising: orderingACK/NACK bits for the at least one scheduled CC based on an index ofeach CC in the plurality of configured CCs.
 11. The method of claim 1,wherein the determining the number of scheduled CCs and the identifierof each scheduled CC comprises detecting a downlink assignment indicator(DAI) in the grant.
 12. The method of claim 11, wherein a size of theDAI is based on a number of configured CCs for the UE.
 13. The method ofclaim 1, wherein determining the number of scheduled CCs and theidentifier of each scheduled CC comprises: obtaining, from the grant, abitmap indicative of the number of scheduled CCs and the identifier ofeach scheduled CC.
 14. The method of claim 13, wherein a number of bitsof the bitmap is less than a number of configured CCs for the UE. 15.The method of claim 13, wherein the plurality of configured CCscomprises a first CC and at least one remaining CC, wherein the grant isfor a data transmission on the first CC, and wherein the bitmapidentifies each scheduled CC in the at least one remaining CC.
 16. Themethod of claim 1, further comprising: determining a number of downlinksubframes in which the UE is scheduled based on the grant; anddetermining ACK/NACK information for data transmissions received on theat least one scheduled CC in the determined number of downlinksubframes, wherein the ACK/NACK information is determined based on thenumber of scheduled CCs, the identifier of each scheduled CC, and thenumber of downlink subframes in which the UE is scheduled.
 17. Themethod of claim 1, wherein determining the ACK/NACK informationcomprises: performing spatial bundling, subframe bundling, CC bundling,or a combination thereof to obtain the ACK/NACK information.
 18. Themethod of claim 1, further comprising: identifying at least one unusedbit based on a number of bits available to send the ACK/NACK informationand a number of bits of the ACK/NACK information to send; and sendinginformation indicating that a grant for one of the scheduled CCs ismissed by the UE using the at least one unused bit.
 19. The method ofclaim 1, further comprising: detecting physical downlink controlchannels (PDCCHs) with grants based on the number of scheduled CCs andthe identifier of each scheduled CC.
 20. The method of claim 1, whereinthe grant comprises a downlink grant for a data transmission on one ofthe at least one scheduled CC or an uplink grant for a data transmissionon an uplink.
 21. The method of claim 1, wherein the plurality ofconfigured CCs is downlink CCs in a wireless network utilizing frequencydivision duplexing (FDD).
 22. The method of claim 1, wherein informationindicative of the number of scheduled CCs and the identifier of eachscheduled CC is received on a primary CC (PCC) for the UE, the PCC beingone of the plurality of configured CCs for the UE.
 23. The method ofclaim 1, wherein information indicative of the number of scheduled CCsand the identifier of each scheduled CC is received on a subset of theplurality of configured CCs for the UE.
 24. An apparatus for wirelesscommunication, comprising: means for receiving a grant on a componentcarrier (CC) in a plurality of CCs configured for a user equipment (UE);means for determining, based on the grant, a number of scheduled CCs andan identifier of each scheduled CC for the UE; and means for determiningacknowledgement/negative acknowledgement (ACK/NACK) information for adata transmission based on the number of scheduled CCs and theidentifier of each scheduled CC.
 25. The apparatus of claim 24, furthercomprising: means for determining a number of ACK/NACK bits for eachscheduled CC based on a transmission mode of the scheduled CC or anumber of transport blocks received on the scheduled CC; and means fordetermining a total number of ACK/NACK bits for the data transmissionbased on the number of ACK/NACK bits for each scheduled CC.
 26. Theapparatus of claim 24, further comprising: means for determining atransmit power for sending the ACK/NACK information based on a totalnumber of ACK/NACK bits for the data transmission; and means for sendingthe ACK/NACK information on a physical uplink control channel (PUCCH)based on the determined transmit power.
 27. The apparatus of claim 24,further comprising: means for determining a number of resource elementsfor sending the ACK/NACK information based on a total number of ACK/NACKbits for the data transmission; and means for sending the ACK/NACKinformation on a physical uplink shared channel (PUSCH) based on thedetermined number of resource elements.
 28. The apparatus of claim 24,wherein the means for determining the number of scheduled CCs and theidentifier of each scheduled CC comprises: means for detecting adownlink assignment indicator (DAI) in the grant.
 29. The apparatus ofclaim 24, wherein the means for determining the number of scheduled CCsand the identifier of each scheduled CC comprises: means for obtaining,from the grant, a bitmap indicative of the number of scheduled CCs andthe identifier of each scheduled CC.
 30. The apparatus of claim 24,wherein the means for determining the ACK/NACK information comprises:means for performing spatial bundling, subframe bundling, CC bundling,or a combination thereof to obtain the ACK/NACK information.
 31. Anapparatus for wireless communication, comprising: at least one processorconfigured to: receive a grant on a component carrier (CC) in aplurality of CCs configured for a user equipment (UE), determine, basedon the grant, a number of scheduled CCs and an identifier of eachscheduled CC for the UE, and determine acknowledgement/negativeacknowledgement (ACK/NACK) information for a data transmission based onthe number of scheduled CCs and the identifier of each scheduled CC; anda memory coupled to the at least one processor.
 32. The apparatus ofclaim 31, wherein the at least one processor is configured to: determinea number of ACK/NACK bits for each scheduled CC based on a transmissionmode of the scheduled CC or a number of transport blocks received on thescheduled CC, and determine a total number of ACK/NACK bits for the datatransmission based on the number of ACK/NACK bits for each scheduled CC.33. The apparatus of claim 31, wherein the at least one processor isconfigured to: determine a transmit power for sending the ACK/NACKinformation based on a total number of ACK/NACK bits for the datatransmission, and send the ACK/NACK information on a physical uplinkcontrol channel (PUCCH) based on the determined transmit power.
 34. Theapparatus of claim 31, wherein the at least one processor is configuredto: determine a number of resource elements for sending the ACK/NACKinformation based on a total number of ACK/NACK bits for the datatransmission, and send the ACK/NACK information on a physical uplinkshared channel (PUSCH) based on the determined number of resourceelements.
 35. The apparatus of claim 31, wherein the at least oneprocessor is configured to detect a downlink assignment indicator (DAI)in the grant.
 36. The apparatus of claim 31, wherein the at least oneprocessor is configured to obtain, from the grant, a bitmap indicativeof the number of scheduled CCs and the identifier of each scheduled CC.37. The apparatus of claim 31, wherein the at least one processor isconfigured to perform spatial bundling, subframe bundling, CC bundling,or a combination thereof to obtain the ACK/NACK information.
 38. Acomputer program product, comprising: a non-transitory computer-readablemedium comprising: code for causing at least one processor to receive agrant on a component carrier (CC) in a plurality of CCs configured for auser equipment (UE), code for causing the at least one processor todetermine, based on the grant, a number of scheduled CCs and anidentifier of each scheduled CC for the UE, and code for causing the atleast one processor to determine acknowledgement/negativeacknowledgement (ACK/NACK) information for a data transmission based onthe number of scheduled CCs and the identifier of each scheduled CC. 39.A method for wireless communication, comprising: generating a grantindicating a number of scheduled component carriers (CCs) and anidentifier of each scheduled CC for a user equipment (UE); sending thegrant on one of a plurality of CCs configured for the UE; sending a datatransmission to the UE on the scheduled CCs; and receivingacknowledgement/negative acknowledgement (ACK/NACK) information from theUE in response to the grant.
 40. The method of claim 39, furthercomprising: determining a number of ACK/NACK bits for each scheduled CCbased on a transmission mode of the scheduled CC or a number oftransport blocks sent on the scheduled CC; and determining a totalnumber of ACK/NACK bits for the data transmission based on the number ofACK/NACK bits for each scheduled CC.
 41. The method of claim 39, furthercomprising: determining a number of resource elements used to send theACK/NACK information based on a total number of ACK/NACK bits for thedata transmission; and receiving the ACK/NACK information on a physicaluplink shared channel (PUSCH) based on the determined number of resourceelements.
 42. The method of claim 39, further comprising: determiningavailable bits for sending channel state information (CSI) based on atotal number of ACK/NACK bits for the data transmission and an availablepayload size; and demultiplexing the CSI and the ACK/NACK informationbased on the available bits for sending the CSI.
 43. The method of claim39, wherein the ACK/NACK information is received from the UE on aphysical uplink control channel (PUCCH) at a transmit powercorresponding to a total number of transport blocks received by the UEin the data transmission.
 44. The method of claim 39, wherein thegenerating the grant comprises: generating the grant comprising a bitmapindicative of the number of scheduled CCs and the identifier of eachscheduled CC.
 45. The method of claim 39, further comprising: schedulingthe UE for data transmission in a subframe based on whether reporting ofchannel state information (CSI) is due from the UE in the subframe. 46.The method of claim 39, further comprising: determining a number of bitsof channel state information (CSI) for reporting by the UE in asubframe; determining a number of bits available to the UE for sendingACK/NACK information in the subframe based on the number of bits of CSI;and scheduling the UE for data transmission in the subframe based on thenumber of bits available to send ACK/NACK information.
 47. An apparatusfor wireless communication, comprising: means for generating a grantindicating a number of scheduled component carriers (CCs) and anidentifier of each scheduled CC for a user equipment (UE); means forsending the grant on one of a plurality of CCs configured for the UE;means for sending a data transmission to the UE on the scheduled CCs;and means for receiving acknowledgement/negative acknowledgement(ACK/NACK) information from the UE in response to the grant.
 48. Theapparatus of claim 47, further comprising: means for determining anumber of ACK/NACK bits for each scheduled CC based on a transmissionmode of the scheduled CC or a number of transport blocks sent on thescheduled CC; and means for determining a total number of ACK/NACK bitsfor the data transmission based on the number of ACK/NACK bits for eachscheduled CC.
 49. The apparatus of claim 47, further comprising: meansfor determining a number of resource elements comprising the ACK/NACKinformation based on a total number of ACK/NACK bits for the datatransmission; and means for receiving the ACK/NACK information on aphysical uplink shared channel (PUSCH) based on the number of resourceelements.
 50. The apparatus of claim 47, further comprising: means fordetermining available bits for sending channel state information (CSI)based on a total number of ACK/NACK bits for the data transmission andan available payload size; and means for demultiplexing the CSI and theACK/NACK information based on a number of the available bits.
 51. Theapparatus of claim 47, wherein the means for generating the grantcomprises: means for generating the grant comprising a bitmap indicativeof the number of scheduled CCs and the identifier of each scheduled CC.52. An apparatus for wireless communication, comprising: at least oneprocessor configured to: generate a grant indicating a number ofscheduled component carriers (CCs) and an identifier of each scheduledCC for a user equipment (UE), send the grant on one of a plurality ofCCs configured for the UE, send a data transmission to the UE on thescheduled CCs, and receive acknowledgement/negative acknowledgement(ACK/NACK) information for the data transmission from the UE in responseto the grant; and a memory coupled to the at least one processor. 53.The apparatus of claim 52, wherein the at least one processor isconfigured to: determine a number of ACK/NACK bits for each scheduled CCbased on a transmission mode of the scheduled CC or a number oftransport blocks sent on the scheduled CC, and determine a total numberof ACK/NACK bits for the data transmission based on the number ofACK/NACK bits for each scheduled CC.
 54. The apparatus of claim 52,wherein the at least one processor is configured to: determine a numberof resource elements comprising the ACK/NACK information based on atotal number of ACK/NACK bits for the data transmission, and receive theACK/NACK information on a physical uplink shared channel (PUSCH) basedon the number of resource elements.
 55. The apparatus of claim 52,wherein the at least one processor is configured to: determine availablebits for sending channel state information (CSI) based on a total numberof ACK/NACK bits for the data transmission and an available payloadsize, and demultiplex the CSI and the ACK/NACK information based on anumber of the available bits.
 56. The apparatus of claim 52, wherein theat least one processor is configured to generate the grant comprising abitmap indicative of the number of scheduled CCs and the identifier ofeach scheduled CC.
 57. A computer program product, comprising: anon-transitory computer-readable medium comprising: code for causing atleast one processor to generate a grant indicating a number of scheduledcomponent carriers (CCs) and an identifier of each scheduled CC for auser equipment (UE), code for causing the at least one processor to sendthe grant on one of a plurality of CCs configured for the UE, code forcausing the at least one processor to send a data transmission to the UEon the scheduled CCs, and code for causing the at least one processor toreceive acknowledgement/negative acknowledgement (ACK/NACK) informationfrom the UE in response to the grant.